Hide Forgot
The pypy package sets a fairly restricted sys.path: ['', '/usr/lib64/pypy-1.6/lib_pypy', '/usr/lib64/pypy-1.6/lib-python/modified-2.7', '/usr/lib64/pypy-1.6/lib-python/2.7', '/usr/lib64/pypy-1.6/lib-python/modified-2.7/lib-tk', '/usr/lib64/pypy-1.6/lib-python/2.7/lib-tk', '/usr/lib64/pypy-1.6/lib-python/2.7/plat-linux2', '/usr/lib64/pypy-1.6/site-packages'] Since it is fully backwards compatible for pure-Python modules, it would be helpful if it included site-packages in its sys.path. I can work around this by setting: export PYTHONPATH="/usr/lib/python2.7/site-packages" However, it seems like it would be a useful for everyone to have this directory included in sys.path by default.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This bug is still present in Fedora 22. The proposed solution is error prone: packages are not only the one installed in "/usr/lib/pythonX.X/site-packages", but there are, for example, also user installed packages (e.g. pip install --user foobar). My pypy3 has the following sys.path: ['', '/usr/lib64/pypy3-2.4.0/lib_pypy/__extensions__', '/usr/lib64/pypy3-2.4.0/lib_pypy', '/usr/lib64/pypy3-2.4.0/lib-python/3', '/usr/lib64/pypy3-2.4.0/lib-python/3/lib-tk', '/usr/lib64/pypy3-2.4.0/lib-python/3/plat-linux2', '/usr/lib64/pypy3-2.4.0/site-packages'] It doesn't take into account user-specific packages. Moreover, it is not clear (documentation missing?) how one should install packages to be used with pypy, in case she/he wants to install them into '/usr/lib64/pypy3-2.4.0/site-packages'. Consider reopening this bug or creating a new one.