[Python-Dev] public visibility of python-dev decisions "before it's too late" (was: PyCObject_AsVoidPtr removed from python 3.2
Terry Reedy
tjreedy at udel.edu
Wed Mar 9 23:22:58 CET 2011
More information about the Python-Dev mailing list
Wed Mar 9 23:22:58 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 3/9/2011 9:50 AM, Tim Lesher wrote: > We used to do biweekly-ish Python-Dev summaries for this reason. They were, is a sense, too detailed, complete, and voluminous. In whatever format, terser announcement of just things others really need to know - like decisions that affect them, would probably be more useful. There is also python-announce, but I do not follow it. -- Terry Jan Reedy
- 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