-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
SAGE_ROOT/tox.ini: Add variants that provision a system python using pyenv #32531
Labels
Comments
comment:2
Remove dependency on #32442, see #29039 comment:163. |
Changed dependencies from #32442 to none |
comment:3
|
Dependencies: #29285 |
This comment has been minimized.
This comment has been minimized.
Upstream: Reported upstream. No feedback yet. |
This comment has been minimized.
This comment has been minimized.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It was suggested (https://groups.google.com/g/sage-devel/c/cSsAsPuVnxg/m/uWEySfvWBQAJ) that testing of new Python versions (such as the upcoming 3.10) could be done via
pyenv
instead of test tickets (such as #30766) that update ourpython3
spkg.In this ticket, we add supporting infrastructure for this in
tox.ini
.Upstream issue:
pythons built with pyenv's python-build leak CFLAGS/LDFLAGS into user packages via sysconfig pyenv/pyenv#2204
python-build
breaks whenMAKE
is set as we document it for Sage (`export MAKE="make -j15"):Depends on #29285
Upstream: Reported upstream. No feedback yet.
CC: @dimpase @orlitzky
Component: porting
Issue created by migration from https://trac.sagemath.org/ticket/32531
The text was updated successfully, but these errors were encountered: