[arch-dev-public] Python move news announcement draft
Hi, I will move python stuff from [testing] soon so we will need a news item... Here is a draft: --begin draft-- Major python update A major python update is hitting the repos on a mirror near you. This involves update the python package from the 2.6 series to the 2.7 series. However, with python-2.7 being scheduled to be the last major release in the python-2.x series, python 2.7 is now packaged as "python2", while the "python" package will contain the python 3.x series. This means that /usr/bin/python will point at python 3.x and any programs requiring python2 should point at /usr/bin/python2 instead. All packages in the repos have been updated, but any issues found can be reported to the bug tracker (not the forum or the mailing lists). Any AUR packages using python will likely need updated to point at the correct python binary. --end draft-- Comments?
On 2010/10/18 Allan McRae <allan@archlinux.org> wrote:
--begin draft--
Major python update
A major python update is hitting the repos on a mirror near you. This involves update the python package from the 2.6 series to the 2.7 series. However, with python-2.7 being scheduled to be the last major release in the python-2.x series, python 2.7 is now packaged as "python2", while the "python" package will contain the python 3.x series. This means that /usr/bin/python will point at python 3.x and any programs requiring python2 should point at /usr/bin/python2 instead. All packages in the repos have been updated, but any issues found can be reported to the bug tracker (not the forum or the mailing lists). Any AUR packages using python will likely need updated to point at the correct python binary.
--end draft--
Comments?
We could add a note saying something like If you installed home-brewed packages in your system, you may find packages that need to be reinstalled by looking for those with files under /usr/lib/python2.6 or matching the regexp '^#!.*python$' -- Rémy
Am 18.10.2010 14:37, schrieb Rémy Oudompheng:
We could add a note saying something like
If you installed home-brewed packages in your system, you may find packages that need to be reinstalled by looking for those with files under /usr/lib/python2.6 or matching the regexp '^#!.*python$'
I agree, we should definitely mention changes to site-specific scripts here (maybe in the same sentence as AUR packages), as lots of them will be affected by this. Thanks for your great work on python.
On Mon, Oct 18, 2010 at 7:32 AM, Allan McRae <allan@archlinux.org> wrote:
Hi,
I will move python stuff from [testing] soon so we will need a news item... Here is a draft:
--begin draft--
Major python update
A major python update is hitting the repos on a mirror near you. This involves update the python package from the 2.6 series to the 2.7 series. However, with python-2.7 being scheduled to be the last major release in the python-2.x series, python 2.7 is now packaged as "python2", while the "python" package will contain the python 3.x series. This means that /usr/bin/python will point at python 3.x and any programs requiring python2 should point at /usr/bin/python2 instead. All packages in the repos have been updated, but any issues found can be reported to the bug tracker (not the forum or the mailing lists). Any AUR packages using python will likely need updated to point at the correct python binary.
--end draft--
Comments?
It might drag on a bit. I'd make it so people don't ignore it; maybe title it so it seems a bit more sensational and people actually read it: "Python 3 is now the default Python". And then make the opening line the bit about packaging and binaries moving rather than all the 2.6 to 2.7 stuff which people will just go "oh, ok, not a big deal" to and miss the python3 stuff completely. -Dan
On 18 October 2010 20:38, Dan McGee <dpmcgee@gmail.com> wrote:
On Mon, Oct 18, 2010 at 7:32 AM, Allan McRae <allan@archlinux.org> wrote:
Hi,
I will move python stuff from [testing] soon so we will need a news item... Here is a draft:
--begin draft--
Major python update
A major python update is hitting the repos on a mirror near you. This involves update the python package from the 2.6 series to the 2.7 series. However, with python-2.7 being scheduled to be the last major release in the python-2.x series, python 2.7 is now packaged as "python2", while the "python" package will contain the python 3.x series. This means that /usr/bin/python will point at python 3.x and any programs requiring python2 should point at /usr/bin/python2 instead. All packages in the repos have been updated, but any issues found can be reported to the bug tracker (not the forum or the mailing lists). Any AUR packages using python will likely need updated to point at the correct python binary.
--end draft--
Comments?
It might drag on a bit. I'd make it so people don't ignore it; maybe title it so it seems a bit more sensational and people actually read it: "Python 3 is now the default Python". And then make the opening line the bit about packaging and binaries moving rather than all the 2.6 to 2.7 stuff which people will just go "oh, ok, not a big deal" to and miss the python3 stuff completely.
Here's an attempt to make it more straightforward. The moving part has been moved to the first few lines so "moved", "default", "3" and "3.x" should register prominently while reading: --begin draft-- Python is now Python 3 A major Python update has just been moved from the testing repositories and will be available on a mirror near you. The default "python" package is now for the 3.x series while the 2.x series has been moved to a "python2" package, with python-2.7 having been scheduled to be the last major release in the python-2.x series. Since /usr/bin/python will now point to the 3.x binary, any program requiring 2.x needs to point to /usr/bin/python2 instead. All our packages have been updated accordingly, but any remaining issues found can be reported to the bug tracker (not the forums or mailing lists). AUR and third-party packages/projects using Python will likely need updating to reflect this move, as many programs are still incompatible with Python 3. --end draft-- And yes, thanks and congrats for a job well done :)
On 19/10/10 01:56, Ray Rashif wrote:
Python is now Python 3
A major Python update has just been moved from the testing repositories and will be available on a mirror near you. The default "python" package is now for the 3.x series while the 2.x series has been moved to a "python2" package, with python-2.7 having been scheduled to be the last major release in the python-2.x series.
Since /usr/bin/python will now point to the 3.x binary, any program requiring 2.x needs to point to /usr/bin/python2 instead. All our packages have been updated accordingly, but any remaining issues found can be reported to the bug tracker (not the forums or mailing lists).
AUR and third-party packages/projects using Python will likely need updating to reflect this move, as many programs are still incompatible with Python 3.
Thanks. Posted and the move is happening now!
On 2010/10/18 Allan McRae <allan@archlinux.org> wrote:
Thanks. Posted and the move is happening now!
Remember to fix luma and lilypond in the process :) -- Rémy.
On 2010/10/18 Allan McRae <allan@archlinux.org> wrote:
On 19/10/10 06:52, Rémy Oudompheng wrote:
On 2010/10/18 Allan McRae<allan@archlinux.org> wrote:
Thanks. Posted and the move is happening now!
Remember to fix luma and lilypond in the process :)
Sure... but can you be any more descriptive than "fix"?
Hum, lilypond is a false positive, but luma was never rebuilt https://bugs.archlinux.org/task/21215
On 19/10/10 06:52, Allan McRae wrote:
On 19/10/10 01:56, Ray Rashif wrote:
Python is now Python 3
A major Python update has just been moved from the testing repositories and will be available on a mirror near you. The default "python" package is now for the 3.x series while the 2.x series has been moved to a "python2" package, with python-2.7 having been scheduled to be the last major release in the python-2.x series.
Since /usr/bin/python will now point to the 3.x binary, any program requiring 2.x needs to point to /usr/bin/python2 instead. All our packages have been updated accordingly, but any remaining issues found can be reported to the bug tracker (not the forums or mailing lists).
AUR and third-party packages/projects using Python will likely need updating to reflect this move, as many programs are still incompatible with Python 3.
Thanks. Posted and the move is happening now!
And the move is done. I think everything that needed moving from [testing] (and nothing that did not...) has now been moved. The only package I am unsure of is libreoffice, but I leave that to Andy to decide. [community-testing] is empty so that is a good sign all packages have been moved! A big thanks to everyone who helped out on this massive rebuild. Allan
On Mon, 18 Oct 2010 22:32:13 +1000 Allan McRae <allan@archlinux.org> wrote:
Hi,
I will move python stuff from [testing] soon so we will need a news item... Here is a draft:
--begin draft--
Major python update
A major python update is hitting the repos on a mirror near you. This involves update the python package from the 2.6 series to the
updating, or "an update"
2.7 series. However, with python-2.7 being scheduled to be the last major release in the python-2.x series, python 2.7 is now packaged as "python2", while the "python" package will contain the python 3.x series. This means that /usr/bin/python will point at python 3.x and
"will contain", "will point" ? when you post this, this will already be the case, no?
any programs requiring python2 should point at /usr/bin/python2 instead. All packages in the repos have been updated, but any issues found can be reported to the bug tracker (not the forum or the mailing lists). Any AUR packages using python will likely need updated to point at the correct python binary.
--end draft--
Comments?
On 18 October 2010 20:39, Dieter Plaetinck <dieter@plaetinck.be> wrote:
On Mon, 18 Oct 2010 22:32:13 +1000 Allan McRae <allan@archlinux.org> wrote:
Hi,
I will move python stuff from [testing] soon so we will need a news item... Here is a draft:
--begin draft--
Major python update
A major python update is hitting the repos on a mirror near you. This involves update the python package from the 2.6 series to the
updating, or "an update"
2.7 series. However, with python-2.7 being scheduled to be the last major release in the python-2.x series, python 2.7 is now packaged as "python2", while the "python" package will contain the python 3.x series. This means that /usr/bin/python will point at python 3.x and
"will contain", "will point" ? when you post this, this will already be the case, no?
This has to do with the fact that nobody will be getting the update immediately: "A major python update is hitting the repos on a mirror near you." But of course, the tenses don't really matter - either is or will be right :p
Am 18.10.2010 16:36, schrieb Ray Rashif:
2.7 series. However, with python-2.7 being scheduled to be the last major release in the python-2.x series, python 2.7 is now packaged as "python2", while the "python" package will contain the python 3.x series. This means that /usr/bin/python will point at python 3.x and
"will contain", "will point" ? when you post this, this will already be the case, no?
This has to do with the fact that nobody will be getting the update immediately:
"A major python update is hitting the repos on a mirror near you."
But of course, the tenses don't really matter - either is or will be right :p
What's new here is that the update will propagate very fast: The package files themselves are already on all mirrors, only a bunch of symlinks will be adjusted - this will be extremely cheap in terms of bandwidth. This is the first major move affected by this recent change.
participants (7)
-
Allan McRae
-
Dan McGee
-
Dieter Plaetinck
-
Ray Rashif
-
Rémy Oudompheng
-
Rémy Oudompheng
-
Thomas Bächler