-
-
Notifications
You must be signed in to change notification settings - Fork 479
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
build/bin/sage-system-python: Try "python" first #29890
Comments
Author: Matthias Koeppe |
This comment has been minimized.
This comment has been minimized.
Commit: |
New commits:
|
Reviewer: John Palmieri |
comment:5
Seems to work with a build from scratch and also building a bunch of optional packages. I didn't see any new breakages with those, just packages which were broken independently of this branch: boost, database_stein_watkins_mini, sage_numerical_backends_cplex, sage_numerical_backends_gurobi, texlive (although why anyone would want to install texlive via Sage is baffling to me). I tested this on OS X using very few system packages, to try out installing as many of Sage's packages as possible (in case some package used Python 3 syntax in its installation process). I used the system's gfortran because of lack of patience, and I used the system's curl because Sage's build of R failed when Sage built its own curl. That is, I used this command:
Was there some quicker way to tell |
comment:6
|
comment:7
Replying to @jhpalmieri:
Unfortunately, no. |
comment:8
Replying to @jhpalmieri:
Probably we should add automatic testing for all optional packages.
(and their dependencies). |
comment:9
The experimental packages are even worse: I tried most of them, and only one ( |
comment:10
Let's continue on #29900 (Meta-ticket: Fix optional and experimental packages for Sage 9.2) |
Branch pushed to git repo; I updated commit sha1 and set ticket back to needs_review. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits: |
comment:13
Sorry, pushed to the wrong ticket. |
Changed branch from u/mkoeppe/build_bin_sage_system_python__try__python__first to |
comment:15
Follow up in #29929 |
Changed commit from |
This is a workaround for a minor annoyance affecting sage developers who update packages on macOS.
python2 urllib works correctly with ssl but the python3 may not (as discussed in #29418). The correct fix is to update
sage_bootstrap
to initialize certificates, or to use a higher-level library for downloading. The workaround to use python2 gives us a bit of time... until Apple removes python2 from the OS.CC: @jhpalmieri
Component: build
Author: Matthias Koeppe
Branch:
1d36a2e
Reviewer: John Palmieri
Issue created by migration from https://trac.sagemath.org/ticket/29890
The text was updated successfully, but these errors were encountered: