You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$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.
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. ↩
The text was updated successfully, but these errors were encountered:
If I install
what gets populated is
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 ofpython3.13t
) and so the build fails1Not sure what's the best approach here, but my understanding would be that this is simply a bug that
SP_DIR
needs to reflect thet
for freethreading builds.CC @isuruf @jjhelmus
Footnotes
I'm not talking about the
pip install
, which works fine (and installs intopython3.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. ↩The text was updated successfully, but these errors were encountered: