Geoffrey Thomas

To be clear #505 is just working around this issue for this repository's own Python code in the build scripts (when the Python interpreter itself is from python-build-standalone)—it's not intended...

Even with `python3 -m venv --copies`, you're still left with a reference in pyvenv.cfg to the original installation's standard library, so I _think_ the premises of 7865 that the given...

OK, with python/cpython#129493 happening, I propose that on the python-build-standalone side we * backport that patch to all existing versions * on all versions, also patch in an `if not...

So there's like three classes of issues that are all very similar-sounding but are not exactly the same thing: * Can the Python _interpreter_ find the e.g. `libpython3.13.so.1.0` _runtime_ library?...

Oh, the thing that confused me is that that issue/change is about whether to build libpython as static or shared, and my question was about the whether the python binary...

I'm taking a look at this in a little more detail. I really want to avoid churning the cache because that has an impact on non-LFS git users, and I...

There is one theoretical backwards-incompatibility here: with current uv, you only have to specify `UV_GIT_LFS=1` _once_ and the checkout and built wheel gets cached with the LFS artifacts included. This...

There is a very old (2002) Debian bug reporting that statically linking libpython is good for performance: https://bugs.debian.org/131813 There too it's about steady-state runtime performance, not startup cost. I _think_...

That makes more intuitive sense to me in that Nuitka compiles what it can, so you're going back and forth between the main program and libpython for the stuff that...

EDIT: this was indeed raised in the Discourse thread already. For symlinks - have you looked at the approach @njsmith took for pybi and the rationale for it? https://github.com/njsmith/posy/blob/main/pybi/README.md#symlinks They...