Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SP_DIR vs. freethreading builds: wrong path? #5563

Open
h-vetinari opened this issue Dec 8, 2024 · 0 comments
Open

SP_DIR vs. freethreading builds: wrong path? #5563

h-vetinari opened this issue Dec 8, 2024 · 0 comments

Comments

@h-vetinari
Copy link
Contributor

If I install

conda install -c conda-forge python-freethreading numpy

what gets populated is

$PREFIX/lib/python3.13t/site-packages/{numpy,...}  # including all the built-in imports
$PREFIX/lib/python3.13/site-packages/pip           # and presumably other noarch packages

However, when trying to build something on top (e.g. scipy), SP_DIR for the free-threading builds doesn't match the main site-package directory (python3.13 instead of python3.13t) and so the build fails1

Not sure what's the best approach here, but my understanding would be that this is simply a bug that SP_DIR needs to reflect the t for freethreading builds.

CC @isuruf @jjhelmus

Footnotes

  1. I'm not talking about the pip install, which works fine (and installs into python3.13t), but we need to manually copy something to $SP_DIR/scipy, due to the way the tests get split off into their own package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant