[Python-Dev] death to 2.7; long live 2.7
Benjamin Peterson
benjamin at python.org
Thu Apr 10 04:02:01 CEST 2014
More information about the Python-Dev mailing list
Thu Apr 10 04:02:01 CEST 2014
- Previous message: [Python-Dev] death to 2.7; long live 2.7
- Next message: [Python-Dev] death to 2.7; long live 2.7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Apr 9, 2014, at 18:46, Senthil Kumaran wrote: > On Wed, Apr 9, 2014 at 9:22 PM, Benjamin Peterson > <benjamin at python.org>wrote: > > > Instead dealing 2.7 will just be completely optional for core > > developers. (The much anticipated vendor support arrives at this point.) > > > > Could you clarify your thoughts a bit on the "completely optional" part. > What if vendors take a really long time to come to support the latest > minor > release? AFAIK, the discussion centered around keep it "alive", for some > definition of alive. We did not define what do we mean by 'alive'. Alive means I will keep making 2.7 releases while there are still interesting changes to release. > > Bringing back all the security related enhancement features seem ok. > Guido's last email talks about all the other compatibility goodies /tools > targeting 2.7 that may or may not go with 2.7 code base itself. I consider the security enhancement/feature question to be in the domain of PEP 466. If security stuff lands in the 2.7 branch, it will get released eventually is all I'm saying.
- Previous message: [Python-Dev] death to 2.7; long live 2.7
- Next message: [Python-Dev] death to 2.7; long live 2.7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list