-----BEGIN PGP SIGNED MESSAGE-----
both Python 2.6 and Python 3.0 final releases are scheduled on Sep 04
, and they are both going into openSUSE 11.1
During this week i'm going to submit Python 2.6 to BETA (and probably
mirror it to BuildService as well), and prepare a Python 3.0 package in
BuildService, called "python3".
Then i will be away for two weeks, and when i return, i'll start moving
things to STABLE/Factory
Python 2.6 is planned to be the last release of 2.x series. It should be
mostly backwards compatible to 2.5, and also forward compatible to 3.0.
Python 3.0, dubbed Py3k, will be massively *backwards incompatible*, and
most of existing python code will not work in it. To ease the
transition, there are two things:
- - "2to3" converter script , which can translate existing 2.x
compatible code to 3.0. The script is part of Python 2.6 release.
- - Python 2.6's __future__ imports and Py3k warnings mode, which, simply
put, turn 2.6 interpreter into 3.0-compatible transition device.
Quoting PEP-361 ():
> Python 2.6 is not only the next advancement in the
> series, it is also a transitional release, helping developers
> begin to prepare their code for Python 3.0. As such, many
> features are being backported from Python 3.0 to 2.6. Thus, it
> makes sense to release both versions in at the same time. The
> precedence for this was set with the Python 1.6 and 2.0 release.
Python 2.x series is slowly going to be deprecated in favor of 3.x
series - but it seems now that it's a matter of years, not months.
1. Python 2.6:
Nothing much to say here, that should be a simple version increase. No
major changes like 2.5's Py_ssize_t mayhem are planned.
/usr/bin/python will be a symlink to /usr/bin/python2.6, and in addition
/usr/bin/python2 will also be a symlink to python2.6.
2. Python 3.0:
This is basically a "new product" which is going to be installed
alongside and not colliding with regular 2.x python.
Its binary will be /usr/bin/python3.0, and a symlink /usr/bin/python3.
No packages depending on python 2.x should be harmed by having py3k
present. Also, there probably won't be any packages depending on py3k yet.
(if you have any comments, please CC me in the reply, otherwise my
replies will break threads. that is a bug in my way of using the
mailinglist, which is not yet fixed)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org