Antoine Pitrou solipsis at pitrou.net
Wed Mar 9 22:14:14 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 19:42:36 +0100
Giampaolo Rodolà <g.rodola at gmail.com> wrote:
> > Actually, why not put up a web page of "upcoming changes" somewhere, that
> > lists major decisions with user impact that were taken on python-dev?
> 
> I think "what's new" serves this purpose properly.
> Usually, every time I commit a new feature, I update the what's new
> file as well.
> In fact we already have a partial "roadmap" for Python 3.3:
> http://docs.python.org/dev/whatsnew/3.3.html

Perhaps the part of the "what's new" document which deals with porting
issues and compatibility breakage would need more highlighting?

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