Contributed by maxime on from the snakes-on-a-plane dept.
On August 31st, Stuart Henderson (sthen@) announced that the default Python version has changed from 2.5 to 2.6. This was following a commit by Federico G. Schwindt (fgsch@) in the ports tree. Please read on for Federico's full commit message and Stuart's announce:
From: "Federico G. Schwindt"
To: firstname.lastname@example.org Subject: CVS: cvs.openbsd.org: ports Date: Mon, 30 Aug 2010 10:35:02 -0600 (MDT) CVSROOT: /cvs Module name: ports Changes by: email@example.com 2010/08/30 10:35:02 Modified files: lang/python : python.port.mk Log message: Switch default to python 2.6. Discussed and ok from many. Bumps will follow.
From: Stuart Henderson
To: ports Subject: HEADS UP: system python changed to 2.6 Date: Tue, 31 Aug 2010 11:33:42 +0100 as you may have noticed the default python version has changed to 2.6. please note: - if you have currently installed ports that use python, you will need to upgrade them before installing new ports using python. if you have a mixture of old+new you will have problems finding libraries. the simplest way to handle this is to use package snapshots and make sure you run pkg_add -ui before adding anything new. if a snapshot contains scapy-2.0.1p0.tgz then it was built against python 2.6. - IF YOU BUILD THINGS FROM PORTS THEN CVS UP THE WHOLE TREE. - if you have created a symlink from /usr/local/bin/python to python2.5, you will almost certainly want to switch it to python2.6, again in order that libraries can be found. (packages should always explicitly use the path to the version of python they were built against; this symlink is a convenience some of you might use for things outside of packages). - test! test! test! several of us have been running with 2.6 as the default python version for a long time and have experienced no problems, but we can't test everything. unlike the switch from 2.4 to 2.5 we don't really expect any incompatibility, but if you rely on something that uses python, then please upgrade when possible and check for problems.
As always, users are invited to test and to report any bug they could find on the ports@ mailing list.
(Comments are closed)