[issue2305] Update What's new in 2.6

Facundo Batista <[EMAIL PROTECTED]> added the comment: The parse_qs() and parse_qsl() relocation from module cgi to urlparse needs an entry in the "What's new..." (alerting you through here, because I commited this last night). See issue 600362 for further info, or ask me directly, :) -

[issue2305] Update What's new in 2.6

A.M. Kuchling <[EMAIL PROTECTED]> added the comment: Closing this item; the 2.6 "What's New" is done, except for any small fixes that get reported. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]>

[issue2305] Update What's new in 2.6

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Thanks for the feedback, I'll do that. I have 50% time instead of 20%, though it doesn't feel that way lately. ;-) ___ Python tracker <[EMAIL PROTECTED]> __

[issue2305] Update What's new in 2.6

A.M. Kuchling <[EMAIL PROTECTED]> added the comment: Oh, and it might be more realistic to keep the 3.0 document as a set of notes, and aim to have a more finished document in 3.1. ISTM it'll be hard to finish writing it in time for a planned 3.0 release, even if you spent your 20% work-time on

[issue2305] Update What's new in 2.6

A.M. Kuchling <[EMAIL PROTECTED]> added the comment: I agree; we don't want to require people to read the 2.6 document, and then the 3.0 document to get a complete picture. Besides, the organization of the 2.x documents may not be suitable for the 3.0 document. The 2.x documents are organized

[issue2305] Update What's new in 2.6

Guido van Rossum <[EMAIL PROTECTED]> added the comment: 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.

[issue2305] Update What's new in 2.6

A.M. Kuchling <[EMAIL PROTECTED]> added the comment: It's in good shape. There are a few items in my saved-email folder that need to be added, and a few XXX markers here and there, but I've done the large stuff, like writing a section on the multiprocessing module. _

[issue2305] Update What's new in 2.6

Guido van Rossum <[EMAIL PROTECTED]> added the comment: How's this coming along? -- versions: +Python 2.6 ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue2305] Update What's new in 2.6

Changes by A.M. Kuchling <[EMAIL PROTECTED]>: -- priority: -> critical ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list

[issue2305] Update What's new in 2.6

Changes by Guido van Rossum <[EMAIL PROTECTED]>: -- assignee: georg.brandl -> akuchling __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list m

[issue2305] Update What's new in 2.6

A.M. Kuchling <[EMAIL PROTECTED]> added the comment: I intend to finish writing the 2.6 document; PyCon has been taking up all of my free time the past few weeks, but obviously that's over now. __ Tracker <[EMAIL PROTECTED]>

[issue2305] Update What's new in 2.6

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: It looks like the author is Kuchling. -- nosy: +akuchling, benjamin.peterson __ Tracker <[EMAIL PROTECTED]> __

[issue2305] Update What's new in 2.6

New submission from Guido van Rossum <[EMAIL PROTECTED]>: Somebody will have to write the "What's new in 2.6" document. I'm doing 3.0 but I'm not doing 2.6 as well. -- assignee: georg.brandl components: Documentation messages: 63591 nosy: georg.brandl, gvanrossum severity: normal status: