Skip to content

Update What's new in 2.6 #46558

Closed
Closed

Description

@gvanrossum
BPO 2305
Nosy @gvanrossum, @akuchling, @birkenfeld, @facundobatista, @benjaminp

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = 'https://github.com/akuchling'
closed_at = <Date 2008-09-04.12:59:19.483>
created_at = <Date 2008-03-16.21:06:08.706>
labels = ['docs']
title = "Update What's new in 2.6"
updated_at = <Date 2008-09-04.13:06:11.618>
user = 'https://github.com/gvanrossum'

bugs.python.org fields:

activity = <Date 2008-09-04.13:06:11.618>
actor = 'facundobatista'
assignee = 'akuchling'
closed = True
closed_date = <Date 2008-09-04.12:59:19.483>
closer = 'akuchling'
components = ['Documentation']
creation = <Date 2008-03-16.21:06:08.706>
creator = 'gvanrossum'
dependencies = []
files = []
hgrepos = []
issue_num = 2305
keywords = []
message_count = 11.0
messages = ['63591', '63599', '63661', '70742', '70753', '70761', '70763', '70764', '70765', '72499', '72500']
nosy_count = 5.0
nosy_names = ['gvanrossum', 'akuchling', 'georg.brandl', 'facundobatista', 'benjamin.peterson']
pr_nums = []
priority = 'critical'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue2305'
versions = ['Python 2.6']

Activity

  1. gvanrossum commented on Mar 16, 2008

    @gvanrossum
    MemberAuthor

    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.

  2. benjaminp commented on Mar 16, 2008

    @benjaminp
    Contributor

    It looks like the author is Kuchling.

  3. akuchling commented on Mar 17, 2008

    @akuchling
    Contributor

    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.

  4. gvanrossum commented on Aug 5, 2008

    @gvanrossum
    MemberAuthor

    How's this coming along?

  5. akuchling commented on Aug 5, 2008

    @akuchling
    Contributor

    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.

  6. gvanrossum commented on Aug 5, 2008

    @gvanrossum
    MemberAuthor

    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"?

  7. akuchling commented on Aug 5, 2008

    @akuchling
    Contributor

    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 by PEP, then a
    section for miscellaneous language changes, then a section for library
    changes. For 3.0, you probably want to do all language changes in one
    section, ignoring how they were broken up into PEPs, then a section on
    the library reorganization, and then maybe sections on using 2to3
    or porting C extensions.

    It's certainly OK with me to copy text from the 2.6 document into the
    3.0 one, if some of the text is useful.

  8. akuchling commented on Aug 5, 2008

    @akuchling
    Contributor

    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 the task.

  9. gvanrossum commented on Aug 5, 2008

    @gvanrossum
    MemberAuthor

    Thanks for the feedback, I'll do that. I have 50% time instead of 20%,
    though it doesn't feel that way lately. ;-)

  10. akuchling commented on Sep 4, 2008

    @akuchling
    Contributor

    Closing this item; the 2.6 "What's New" is done, except for any small
    fixes that get reported.

  11. facundobatista commented on Sep 4, 2008

    @facundobatista
    Member

    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 bpo-600362 for further info, or ask me directly, :)

  12. transferred this issue fromon Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

docsDocumentation in the Doc dir

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions