This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients akuchling, benjamin.peterson, georg.brandl, gvanrossum
Date 2008-08-05.19:39:41
SpamBayes Score 0.08675373
Marked as misclassified No
Message-id <1217965186.1.0.173362838072.issue2305@psf.upfronthosting.co.za>
In-reply-to
Content
Great!  The same cannot be said of the 3.0 version, which is on my plate.

I wonder if you have an opinion on what to do with features that were
initially targeted for 3.0 and then backported to 2.6.  Should these
appear in "what's new in 2.6", in "what's new in 3.0", or in both?  I'm
thinking that perhaps these should appear in both, for the benefit of
folks planning to jump straight into 3.0 from 2.5.  After all, 2.6 and
3.0 are coming out at the same time.  Or should be just add these to 2.6
and add a generic clause to the 3.0 document saying "also see the 2.6
document"?
History
Date User Action Args
2008-08-05 19:39:46gvanrossumsetrecipients: + gvanrossum, akuchling, georg.brandl, benjamin.peterson
2008-08-05 19:39:46gvanrossumsetmessageid: <1217965186.1.0.173362838072.issue2305@psf.upfronthosting.co.za>
2008-08-05 19:39:42gvanrossumlinkissue2305 messages
2008-08-05 19:39:41gvanrossumcreate