Summary: | python and >=linux-3 don't play well | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dirkjan Ochtman (RETIRED) <djc> |
Component: | New packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | flow, nikoli |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 374579, 375253, 375255, 378401, 387047 |
Description
Dirkjan Ochtman (RETIRED)
![]() Note: for 99% of python packages out there, linux-3 issues can be fixed by s/sys.platform == 'linux2'/sys.platform.startswith('linux')/ Will you apply http://hg.python.org/cpython/rev/c816479f6aaf/ (perhaps minus the NEWS changes, as they won't apply as easily) to all python versions supported by Gentoo? That minimizes breakage of existing code and still allows people to update their kernel to linux 3. (In reply to comment #2) > Will you apply http://hg.python.org/cpython/rev/c816479f6aaf/ (perhaps minus > the NEWS changes, as they won't apply as easily) to all python versions > supported by Gentoo? That minimizes breakage of existing code and still allows > people to update their kernel to linux 3. I think it is the best solution there is: take an upstream fix (though it's arguably not that good). More and more bugs would appear (for example, Mercurial build is broken with sys.platform=='linux3'), and the sooner we roll back to 'linux2' as upstream had done, the less bugs would bother users. I've started by adding 2.7.2-r3 and 3.1.4-r3 with the patch from upstream. Will see about older versions on the gentoo-python mailing list. gentoo-sources-3.0.6 are now marked amd64 stable, do you plan to stabilize python-2.7.2-r3 and 3.1.4-r3? Since there have been no complaints about python:2.5 and python:2.6, closing. |