[Python-Dev] public visibility of python-dev decisions "before it's too late" (was: PyCObject_AsVoidPtr removed from python 3.2
Antoine Pitrou
solipsis at pitrou.net
Fri Mar 11 23:00:42 CET 2011
More information about the Python-Dev mailing list
Fri Mar 11 23:00:42 CET 2011
- Previous 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?)
- 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 Wed, 9 Mar 2011 15:40:56 -0500 Doug Hellmann <doug.hellmann at gmail.com> wrote: > > The original request from the board was for the communications team to write the messages, but I think it is more appropriate for the people doing the work to talk about it. [...] > > I asked Michael to add this topic to the agenda for the language summit tomorrow to get early feedback about whether this group thinks it is a good idea. If you find someone who likes to do it then it's fine. Otherwise, I'm not sure it's a good use of our (the developers') time. We already explain changes in the documentation, in Misc/NEWS and in the "what's new" documents... Regards Antoine.
- Previous 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?)
- 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