python-build-standalone VS iron.nvim

It also replaces "just" as a task manager for me which is very pleasant.

The fact that the python plugin uses precompiled Python binaries by default instead of building them from source remove common issues I had with the asdf's python plugin at work with missing dependencies.

Just so you know, I encountered two little quirks that needed a fix:

- [Backspace Key Doesn't work in Python REPL](https://github.com/indygreg/python-build-standalone/blob/mai...)

These builds are an alternative: https://github.com/indygreg/python-build-standalone

Those are what Rye and hatch use.

Drawbacks: late availability of patch versions, various quirks from how they are built (missing readline, missing some build info that self-compiled C python modules might need.)

Bundling Python isn't too bad if you find the right tools for it.

I really like https://github.com/indygreg/python-build-standalone and https://github.com/indygreg/PyOxidizer

A bundled, built standalone Python can be 16 to 32MB (including the full standard library, which you can strip down to just the bits you use to save size). Not tiny, but probably not worth switching programming languages over.

I'm trying to build a "portable" Python package based on those available from https://github.com/indygreg/python-build-standalone/releases.

I'm a huge fan of https://github.com/indygreg/python-build-standalone which provides Python builds that CAN be moved around and work independently of any other Python installation.

I used that for my own Python+Electron app, which I wrote about here: https://til.simonwillison.net/electron/python-inside-electro...

I used to build my own Pythons that are the same everywhere, now I use indygreg's Python builds. Rye will automatically download and manage Python builds from there. No compiling, no divergence.

One interesting tidbit is that it completely ignores your system Python installations, and instead uses precompiled installations of Python by indygreg from PyOxidizer. This means you don't have to deal with installing Python. It just auto downloads the right builds.

wget https://github.com/indygreg/python-build-standalone/releases/download/20220630/cpython-3.10.5+20220630-x86_64_v3-unknown-linux-gnu-install_only.tar.gz -O - | tar -xz && mv python PortablePython

The lack of Ruby support instantly rings an alarm for me because CPython (on POSIX) also is not relocatable, but is listed as support. Turns pit Hermit is actually using a third-party build script[1] instead of the official one. While the python-build-standalone project is quite awesome and indeed is useful for a lot of things, it has enough quirks I would recommend against any generic package distributor to advertise as Python for general use. This in turn makes me lose most confidence on Hermit, unfortunately.

Be careful if you’re also interested in Hermit. These kinds of things bit you up way down the road when you least expect them to.

[1] https://github.com/indygreg/python-build-standalone

If you really want to be sure, you can download an install_only standalone Python build from https://github.com/indygreg/python-build-standalone/releases and install the libraries with the included pip. Then just tar it again to archive it, and use the included python to run your project. The downloaded wheel you get with pip wheel may depend on the Python version so you just save the wheels you must make sure the Python point version is exactly the same.

hard to tell, could be iron maybe? https://github.com/Vigemus/iron.nvim

The plugin in question is iron.nvim - but my question is certainly also applicable to other uses. How do I figure this out?

Hey all, I've been thinking a lot about it and I believe I'm not being fair to the (relatively big) community that formed around iron.nvim and I think it needs a more active maintainer. I'd love to have the time and energy to put the effort into zero-ing the issues and delivering more features, keeping up with neovim development, but unfortunately it is not possible.

For the record/list, there's also: - https://github.com/hkupty/iron.nvim and - https://github.com/jpalardy/vim-slime

For Codi, I migrated away to iron.nvim. Codi is really slick though :)

In the past, when I was using NeoVim more, I also used iron.nvim: https://github.com/hkupty/iron.nvim