[Python-Dev] public visibility of python-dev decisions "before it's too late"
Senthil Kumaran
orsenthil at gmail.com
Wed Mar 16 03:32:55 CET 2011
More information about the Python-Dev mailing list
Wed Mar 16 03:32:55 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"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Mar 15, 2011 at 10:14:12PM -0400, Lennart Regebro wrote: > Up until the reactions from the core Python developers on these real > world problems, it was hard work, but also fun. It is still. The majority of the responses were informative on backwards compatibility and release process. And suggestive of how things changed from between 2.7, 3.1 and 3.2. And there is a unique problem here that 3.1 was released before 2.7. And things which break backwards compatibility is discussed before any changes are made. So, your comment on python 'always breaking the compatibility' was not correct and perhaps that invoked a strong reaction. -- Senthil
- 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"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list