[opensuse-factory] Python 2.7 coming to Factory
Fellow developers and users, just a heads-up: moments ago I have submitted a new Python version 2.7. This version contains many new and interesting features, and only a small chance of breaking existing code: no backwards-incompatible changes, and no big changes worth mentioning. For more details see [1]. There is one thing notable for people who write or maintain software that embeds Python: the new function PySys_SetArgvEx [2] does the job originally done by PySys_SetArgv, but closes a nasty security problem with the latter [3][4]. Most software should be fixed by now, but please review your packages anyway. have fun m. [1] http://docs.python.org/dev/whatsnew/2.7.html#porting-to-python-2-7 [2] http://docs.python.org/dev/c-api/init.html#PySys_SetArgvEx - the link points to python 3 docs, but applies to 2.7 as well [3] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5983 [4] http://www.openwall.com/lists/oss-security/2009/01/26/2 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2010/8/27 Jan Matejek <jan.matejek@novell.com>:
Yes! I am glad to see this. -- Jon -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2010/8/27 Jan Matejek <jan.matejek@novell.com>:
It's great to see this. Is there any way that I can test this? When I try to install it, it causes conflicts with almost all Python packages on my system as they all seem to require either "python = 2.6" or "python(abi) = 2.6". Cheers, Matt -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Dne 3.9.2010 13:10, Matt Williams napsal(a):
depends on how much "testing" you want to be able to do. you can, for example, install python 2.7 from rpms by issuing: rpm -ivh --force python-*.rpm libpython*.rpm (not sure if you can do this through zypper) this way, by using "install" instead of "upgrade" action, you get files from python 2.6 alongside files from python 2.7 but you will break applications, because they have parts in /usr/lib64/python2.6 and the new interpreter will be looking in python2.7 you can fix this in two ways: a) relink /usr/bin/python to /usr/bin/python2.6 and use python2.7 only explicitly b) create a file /usr/lib64/python2.7/site-packages/python2.6.pth, with one line: /usr/lib/python2.6/site-packages (yes, that's /usr/lib even for 64bit machine) this way, you'll force python 2.7 interpreter to look for missing bits in python2.6 directories. applications with binary modules will still be broken and you'll need to run the old interpreter, but noarch applications should be ok. hope this helps m.
Cheers, Matt
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2010/8/27 Jan Matejek <jan.matejek@novell.com>:
Yes! I am glad to see this. -- Jon -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2010/8/27 Jan Matejek <jan.matejek@novell.com>:
It's great to see this. Is there any way that I can test this? When I try to install it, it causes conflicts with almost all Python packages on my system as they all seem to require either "python = 2.6" or "python(abi) = 2.6". Cheers, Matt -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Dne 3.9.2010 13:10, Matt Williams napsal(a):
depends on how much "testing" you want to be able to do. you can, for example, install python 2.7 from rpms by issuing: rpm -ivh --force python-*.rpm libpython*.rpm (not sure if you can do this through zypper) this way, by using "install" instead of "upgrade" action, you get files from python 2.6 alongside files from python 2.7 but you will break applications, because they have parts in /usr/lib64/python2.6 and the new interpreter will be looking in python2.7 you can fix this in two ways: a) relink /usr/bin/python to /usr/bin/python2.6 and use python2.7 only explicitly b) create a file /usr/lib64/python2.7/site-packages/python2.6.pth, with one line: /usr/lib/python2.6/site-packages (yes, that's /usr/lib even for 64bit machine) this way, you'll force python 2.7 interpreter to look for missing bits in python2.6 directories. applications with binary modules will still be broken and you'll need to run the old interpreter, but noarch applications should be ok. hope this helps m.
Cheers, Matt
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
Jan Matejek -
Jon Nelson -
Matt Williams