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
Python3 is broken on OS X #22756
Comments
This comment has been minimized.
This comment has been minimized.
Branch: u/jhpalmieri/python3_osx |
comment:3
Here is a start, but it doesn't fix the problem with Python 2 breaking Python 3, since I don't know what's going on. I bumped the version number to force a rebuild, since anyone using OS X is likely to currently have a broken Python 3 build. New commits:
|
Commit: |
comment:4
By the way, some of the changes were just to decrease differences between the
and the lines surrounding
This second one is broken even for |
comment:5
The error with |
comment:6
You're right. If I build |
comment:7
Do we need the symlink (in Well, I'll try building without and see what happens. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Dependencies: #22764 |
This comment has been minimized.
This comment has been minimized.
comment:10
Removing the symlink works for me. See #22764. I've made that a dependency. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:12
I am OK with this but I definitely want to wait for feedback on #22764. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:14
With the branch here, I am having problems building
The
and then proceeds to try to build. Then later it has this:
I don't know if these are tied to the branch here or not, since I haven't been able to build python3 without the changes here. |
comment:15
Hum... for matplotlib, that particular file is an objective-C module. We would have to build gcc with support for it or use native clang. fpylll should build with python3, although I am still at 3.4 in gentoo but I believe upstream tests 3.5. It feels like there is something missing in the python install regarding unicode support. Would have to check python's log. |
comment:16
I should have said: the problems with |
comment:17
Was clear to me. My comments still stand. |
comment:18
Building |
Attachment: python3-3.5.1.p0.log |
comment:19
Python 3 log attached. I noticed at the beginning:
We should probably remove those options, either here or on another ticket. |
comment:41
ping? |
comment:42
Sure, I think it can go in that state. Then I can some more stuff to both python2 and 3 later. Hope I can get around to it. |
comment:43
Thank you! Regarding clang and Python on OS X: I installed gcc 5.4.0 on a machine the other day, and then with #12426, |
comment:44
Replying to @jhpalmieri:
Interesting experience. #12426 can still be tweaked, but yes we may want to prevent users to shoot themselves too much in the foot. While I don't want to impose things too strongly, I am very much of a mind to put my foot down on the compiler to be used on OS X. |
comment:45
Reviewer name... |
Reviewer: François Bissey |
comment:46
Sorry, I really should know better. |
comment:47
Replying to @kiwifb:
Right now we build |
comment:48
By the way, thank you for your help with this ticket. Many parts of the branch came from your suggestions. |
comment:49
Author name... |
comment:50
Replying to @kiwifb:
Me too. |
Author: John Palmieri |
Changed branch from u/jhpalmieri/python3_osx to |
On OS X, Python3 sometimes fails to build correctly. To fix this:
make
xz
a dependency: not necessary for Python 3 to build, but this way it builds the_lzma
module.use
clang
to compile Python 3, as we do for Python 2. Without this, the_scproxy
module fails to build.patch
Include/pyport.h
as we do for Python 2 -- see pyport.h from python2.7 sometimes clashes with c++ functions on OS X #22147, and also https://trac.macports.org/ticket/44288 and http://bugs.python.org/issue10910.do not create a symlink
SAGE_LOCAL/lib/python
-- see Remove the link SAGE_LOCAL/lib/python #22764. If this symlink is in place and if Python 2 is built before Python 3, then Python 3 picks up that link in its load path, and so it tries to read a lot of Python 2 packages, which is bad.see also Python 3 and OS X metaticket #22781 which tracks a few other issues related to Python 3, OS X, and Sage packages.
Depends on #22764
Component: python3
Author: John Palmieri
Branch/Commit:
6762fe4
Reviewer: François Bissey
Issue created by migration from https://trac.sagemath.org/ticket/22756
The text was updated successfully, but these errors were encountered: