Upgrade to Python 2.7

[GoogleCodeExporter]

Hello,
are there any blockers against upgrading to Python 2.7?

Best regards.

Original issue reported on code.google.com by tim.mich...@gmail.com on 23 Aug 2010 at 7:55

[GoogleCodeExporter]

Many users would prefer a more stable release - note that 2.6.6 is about to 
come out, which shows how long it takes for releases to become stable.  When 
python(x,y) upgraded to 2.6.3 (I think) there were some unexpected nasty 
surprises, so it is better to wait a while and make sure a similar problem does 
not occur again.

Original comment by DavidAnt...@gmail.com on 23 Aug 2010 at 12:39

[GoogleCodeExporter]

I agree, this is far too soon to switch to Python 2.7.

Original comment by pierre.raybaut on 24 Aug 2010 at 11:57

[GoogleCodeExporter]

Vim7.3 only support python2.7, and I wanna Python(x,y) will be upgrading to 
Python 2.7 as soon as possible.

Original comment by yankCh...@gmail.com on 12 Oct 2010 at 1:33

[GoogleCodeExporter]

I'd suggest that while stability is important, there are some that would like a 
convenient way of getting "experimental" (from the PythonXY perspective) 
packages (e.g. Python 2.7, Python 3.X, PyQt > 4.5, etc.) so long as said 
packages are clearly marked as experimental - meaning not thoroughly tested by 
the PythonXY maintainers.

Along those lines, it would be a good idea to start putting together a Python 3 
distribution of PythonXY, since Python2.7 is the last of the Python 2 series.  
In doing so, you should also allow the PythonXY 2 and PythonXY 3 distributions 
to be installed side-by-side so that individuals can work on porting their code 
from one to the other.

Original comment by airdrik@gmail.com on 3 Dec 2010 at 4:18

[GoogleCodeExporter]

Hey - since python 2.7.1 is already out - what are the plans on moving to this 
version? It is important to me (and to others, I guess) to use a late version 
of python (especially since 2.7 is more compliant with the 3.1 versions)

Original comment by Tsvi...@gmail.com on 13 Jan 2011 at 5:30

[GoogleCodeExporter]

One advantage of moving to 2.7 would be compatibility with OpenCV2.2. The 
OpenCV2.1 documentation is marginal, and moving to Python 2.7 would allow 
inclusion of the better documented OpenCV2.2.

Original comment by thomas.h...@gmail.com on 5 Feb 2011 at 6:51

[GoogleCodeExporter]

Unless Pierre objects, once 2.6.6.0 is out of the door we'll start working on 
moving everything to 2.7.

Original comment by grizzly.nyo on 5 Feb 2011 at 6:55

• Changed state: Accepted
• Added labels: Priority-High, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Original comment by grizzly.nyo on 19 Feb 2011 at 6:27

• Added labels: Milestone-Release2.7.1.0

[GoogleCodeExporter]

Original comment by grizzly.nyo on 19 Apr 2011 at 8:56

• Changed state: Started

[GoogleCodeExporter]

Original comment by grizzly.nyo on 2 Jul 2011 at 6:10

• Added labels: Milestone-Release2.7.2.0, Type-Task
• Removed labels: Milestone-Release2.7.1.0, Type-Enhancement

[GoogleCodeExporter]

Do you have a list of blocking packages? And could someone give a very rough 
ETA for moving to 2.7?  (Many of us need access to a recent version of Python)

Original comment by spmciner...@hotmail.com on 31 Jul 2011 at 3:15

[GoogleCodeExporter]

Hi,

The 2.7 branch is public - you can follow the porting progress there. See
also the issue list for pending tasks.

In a nutshell, there are about 6 packages left to update to 2.7 and about 6
package to update to a new version.

-gabi

Original comment by grizzly.nyo on 31 Jul 2011 at 6:14

[GoogleCodeExporter]

Original comment by grizzly.nyo on 4 Sep 2011 at 12:25

• Changed state: Fixed