2010/8/27 Jan Matejek
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
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