[python-committers] Why r69846 is not merged to"release26-maint"?
Benjamin Peterson
benjamin at python.org
Fri Jul 3 01:30:39 CEST 2009
More information about the python-committers mailing list
Fri Jul 3 01:30:39 CEST 2009
- Previous message: [python-committers] Why r69846 is not merged to"release26-maint"?
- Next message: [python-committers] Why r69846 is not merged to"release26-maint"?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2009/7/2 Christian Heimes <christian at cheimes.de>: > Barry Warsaw wrote: >> I will announce this to py-list, py-ann, and update the 3.0 download pages. >> >> There will be no 3.0.2. > > +1 for your decision. > > Are there any known incompatibilities that could break a Python 3.0 > script on 3.1? This is the short list: http://docs.python.org/dev/py3k/whatsnew/3.1.html#porting-to-python-3-1 I'm sure there's a variety of py3k transition problem fixes that break strict compatibility, though. -- Regards, Benjamin
- Previous message: [python-committers] Why r69846 is not merged to"release26-maint"?
- Next message: [python-committers] Why r69846 is not merged to"release26-maint"?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list