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
When building Python on OS X, test whether _scproxy can be imported successfully. #21685
Comments
Branch: u/jhpalmieri/test_scproxy |
New commits:
|
Commit: |
comment:3
Is there a way to test before installing python? Once python is installed you are screwed, so it should happen before, or possibly start the clean up. |
comment:4
I don't know enough about the Python build process to know how to test before it is installed. We can uninstall if it fails, though. |
comment:5
I'll look to see if there is an easy way to figure out before installing. |
comment:6
From the "src" folder
So we should abort if |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:9
Great, that's better than what I was doing. I'm wary of deleting things, so I've removed that part of my changes. I think we can still test for |
comment:10
I just tested this on OS X 10.12 with and without my branch from #21567 (so with Python succeeding and failing to build |
comment:11
Looks good to me. |
Reviewer: François Bissey |
Changed branch from u/jhpalmieri/test_scproxy to |
On OS X 10.12, and also with some earlier versions of OS X, we have had problems with the Sage build because Python claimed to build correctly even though the module
_scproxy
did not actually build. So let's test to make sure.Component: packages: standard
Author: John Palmieri
Branch/Commit:
791ed00
Reviewer: François Bissey
Issue created by migration from https://trac.sagemath.org/ticket/21685
The text was updated successfully, but these errors were encountered: