Skip to content

Rename the thread module to _thread #47124

Closed

Description

@brettcannon
BPO 2875
Nosy @brettcannon, @birkenfeld

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 = None
closed_at = <Date 2008-05-25.13:06:32.277>
created_at = <Date 2008-05-16.04:46:44.858>
labels = ['type-bug', 'library', 'release-blocker']
title = 'Rename the thread module to _thread'
updated_at = <Date 2008-05-26.17:33:17.847>
user = 'https://github.com/brettcannon'

bugs.python.org fields:

activity = <Date 2008-05-26.17:33:17.847>
actor = 'brett.cannon'
assignee = 'none'
closed = True
closed_date = <Date 2008-05-25.13:06:32.277>
closer = 'georg.brandl'
components = ['Library (Lib)']
creation = <Date 2008-05-16.04:46:44.858>
creator = 'brett.cannon'
dependencies = []
files = []
hgrepos = []
issue_num = 2875
keywords = []
message_count = 7.0
messages = ['66899', '67088', '67347', '67355', '67356', '67367', '67377']
nosy_count = 2.0
nosy_names = ['brett.cannon', 'georg.brandl']
pr_nums = []
priority = 'release blocker'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue2875'
versions = ['Python 3.0']

Activity

  1. brettcannon commented on May 16, 2008

    @brettcannon
    MemberAuthor

    PEP-3108 has thread slated to be renamed _thread (along with dummy_thread
    to _dummy_thread).

  2. added
    stdlibStandard Library Python modules in the Lib/ directory
    type-bugAn unexpected behavior, bug, or error
    on May 16, 2008
  3. brettcannon commented on May 20, 2008

    @brettcannon
    MemberAuthor

    Renames are only occurring in 3.0, not 2.6.

  4. birkenfeld commented on May 25, 2008

    @birkenfeld
    Member

    Done in r63631. Fixer added in r63627 and r63629, notices to 2.6 docs
    added in r63630.

    Do you still want to warn when importing thread or dummy_thread directly
    in 2.6, like PEP-3108 says?

  5. brettcannon commented on May 26, 2008

    @brettcannon
    MemberAuthor

    Yeah, it is essentially a deprecation so the warning should be there.

  6. brettcannon commented on May 26, 2008

    @brettcannon
    MemberAuthor

    But then again I thought that about the renames. =) Someone might actually
    pickle something from thread, so not sure how best to handle this one.

  7. birkenfeld commented on May 26, 2008

    @birkenfeld
    Member

    Then I suggest to do the same thing as for all the other renames,
    leaving only the notice in the docs.

  8. brettcannon commented on May 26, 2008

    @brettcannon
    MemberAuthor

    On Mon, May 26, 2008 at 1:45 AM, Georg Brandl <report@bugs.python.org> wrote:

    Georg Brandl <georg@python.org> added the comment:

    Then I suggest to do the same thing as for all the other renames,
    leaving only the notice in the docs.

    Works for me.

  9. 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

No one assigned

    Labels

    release-blockerstdlibStandard Library Python modules in the Lib/ directorytype-bugAn unexpected behavior, bug, or error

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions