[Python-Dev] public visibility of python-dev decisions "before it's too late"
Ronald Oussoren
ronaldoussoren at mac.com
Wed Mar 16 14:04:48 CET 2011
More information about the Python-Dev mailing list
Wed Mar 16 14:04:48 CET 2011
- Previous message: [Python-Dev] public visibility of python-dev decisions "before it's too late"
- Next message: [Python-Dev] public visibility of python-dev decisions "before it's too late" (was: PyCObject_AsVoidPtr removed from python 3.2 - is this documented?)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 15 Mar, 2011, at 19:31, Greg Ewing wrote: > Martin v. Löwis wrote: > >> "There must be at least a one-year transition period between the >> release of the transitional version of Python and the release >> of the backwards incompatible version. > > I still think this is going to result in rude shocks to > people switching from 2 to 3 and jumping several releases > into the 3.x line. You need to update the source of extensions anyway when switching from 2.x to 3.x, this additional change is a minor one. Ronald
- Previous message: [Python-Dev] public visibility of python-dev decisions "before it's too late"
- Next message: [Python-Dev] public visibility of python-dev decisions "before it's too late" (was: PyCObject_AsVoidPtr removed from python 3.2 - is this documented?)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list