Zanie Blue
Zanie Blue
There shouldn't be false negatives from the `sysconfig` prefix variable, unless of course, the build process changes. I'm not opposed to setting something specific to reflect that it's a `python-build-standalone`...
The standalone distributions do need to be special cased though, i.e., `sysconfig` is _known_ to be broken and installers (or other consumers) need to understand that and adjust their behavior...
In uv we use https://github.com/astral-sh/uv/blob/c25c800367a5f43069f1c9d778cfd5de1bcc54a6/crates/uv-python/python/get_interpreter_info.py#L639-L645 However, we patch that install time https://github.com/astral-sh/uv/blob/3bb8ac610ca5690fce0eea9da792dbe6eecaad05/crates/uv-python/src/sysconfig/mod.rs#L206 We should insert that into sysconfig in this repository.
Ah we can't do this until the next release because we use the previous uv version to bootstrap Python versions and that has a different 3.13 (rc)
I think we could wait a week or two to merge this so it doesn't block uv builds for downstream distributors?
Casually posting a solution to this very hard problem on a Sunday! Can't wait to give it a look.
Hi! Sounds like your dependency `mujoco` requires CMake to build — you'll need to install that on your system, Rye cannot do so.
Ah okay. `which cmake` returns a path? That's weird then. This still shouldn't be something related to Rye; `cmake` isn't being found by the `mujoco` build script so you'll need...
(I'll review this)
Just to clarify, you expect all of the files to have 0c644 permissions instead of 0c664 to match the upstream behavior?