-
-
Notifications
You must be signed in to change notification settings - Fork 482
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
linux kernel 3.0 causes headaches with some python modules #11619
Comments
comment:1
Haha. First step is perhaps to create a symbolic link from |
comment:2
That's the kind of solution debated (well copying not linking. More fun is the checking for linux2:
ipython, distutils, numpy, scipy, sympy, networkx, sqlalchemy and twisted. And there are stuff that don't install in site-packages like scons.
I think that's a check for the intel compiler so we shouldn't worry about that one.... |
comment:3
Well, the impact seems to be less hard, as So any Python installation / binary package built on a 2.x kernel should work seamlessly on a 3.x one. Still funny to read the discussion at the Python BTS. |
comment:4
Replying to @kiwifb:
There's also (in the Sage installation):
|
comment:5
This is now "fixed" by upstream by only using |
Changed upstream from Reported upstream. Developers acknowledge bug. to Completely fixed; Fix reported upstream |
Reviewer: Jeroen Demeyer |
This is quite fun. Python setup looks at linux major version number and will build some modules in a folder normally called plat-linux2. With linux 3.0 it looks for the non-existent plat-linux3.
Upstream report is here:
http://bugs.python.org/issue12326
Not completely sure if there are implication for sage or any of its components apart from matplotlib where they updated some code to avoid the problem:
matplotlib/matplotlib@aaef944
One of main problem is that a lot of packages use
when they should use something like
So we will have to fix python (I will do something in #9958 once I figured out what upstream is doing) and potentially some other packages which are looking for linux2.
I think it is too late to do something for 4.7.1 but we should look into fixing 4.7.2.
Upstream: Completely fixed; Fix reported upstream
Component: packages: standard
Reviewer: Jeroen Demeyer
Issue created by migration from https://trac.sagemath.org/ticket/11619
The text was updated successfully, but these errors were encountered: