Rye's shims break cargo test? (Is this a bug, or have I just broken something ...)

[brettc]

Hi. I'm converting a python/c++ project to a python/rust project, and it has been going great. I'm experienced with python/c++, but a rust noob. I'm using rye / pyo3.rs, working with ndarray / numpy, and it all just works. Or did, until today. I'm not even sure what I did to break it. But here is what happens:

• rye sync works
• maturin develop works fine
• cargo test fails with ld: library 'python3.12' not found
• same with cargo bench
• If I uninstall rye self uninstall, then the cargo commands work fine.
• So it seems like it is a problem with the shims being there...?

Note 1: I've uninstalled/reinstalled rust/rye/python and it persists.
Note 2: I have even replicated the problem on another Mac mini m1. So it isn't just my laptop.

Tech deets:
Apple M2 Pro
Sonoma: 14.3.1 (23D60)
rye 0.28.0
Python 3.12.2

Any hints, or revelations of the obvious that I have stupidly overlooked, would be appreciated.

[bluss]

This might be issue #646

[bluss]

It could be that it's looking at the pkgconfig file or so, that also needs to be patched. I think rye can solve this patching eventually, but it's not a super quick fix.

[gauravkumar37]

Folks stumbling on this issue and trying out the monkey_patch_sysconfig above. It works 🚀
However, if you are using it inside cargo, print to stdout is reserved so either comment the print statement or redirect it to stderr
print(..., file=sys.stderr)

Or just use https://github.com/bluss/sysconfigpatcher

[bluss]

the successor to that patch function is https://github.com/bluss/sysconfigpatcher which is a little bit less hacky (but not much)

[gauravkumar37]

Yes, I just edited my comment. The instructions weren't super clear on the repo. Here's what I did:

$ python3 -c 'import sysconfig; print(sysconfig.get_config_var("LIBDIR"))'
/install/lib

$ uv python find --system
/home/ec2-user/.local/share/uv/python/cpython-3.11.10-linux-x86_64-gnu/bin/python3

$ sysconfigpatcher /home/ec2-user/.local/share/uv/python/cpython-3.11.10-linux-x86_64-gnu

$ python3 -c 'import sysconfig; print(sysconfig.get_config_var("LIBDIR"))'
/home/ec2-user/.local/share/uv/python/cpython-3.11.10-linux-x86_64-gnu/lib

[bluss]

Great. For convenience there is also python -m sysconfig | grep LIBDIR

[brettc]

What I cannot figure out is why it worked fine for the last 2 months, and then suddenly broke. I suspect I must have had the "right" python libs available on my path somehow.