On Tue, Mar 20, 2007 at 06:08:24AM +0100, neal.norwitz wrote: > Author: neal.norwitz > Date: Tue Mar 20 06:08:23 2007 > New Revision: 54457 > > +% Should there be a new section here for 3k migration? > +% Or perhaps a more general section describing module changes/deprecation? > +% sets module deprecated
This is an interesting question: should the "What's New" talk about Python 3000? My initial tentative reaction is 'no', because a Py3K section would need to continue to be updated as Python 3000's definition shifts. Once previous Python 2.x versions were released, "What's New" documents became very static, the only changes being typo fixes and small corrections and clarifications. Having to continually update the Py3K section would be annoying, and argues for a separate document that isn't necessarily tied to Python 2.x releases. On the other hand, it would be nice to warn users away from idioms that will break in Py3K, and the "What's New" is a natural place to do it. Hm. But the 'porting' section already talks about features that are being deprecated; is that enough? Thoughts? --amk _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
