You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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=Noneclosed_at=<Date2008-05-25.13:06:32.277>created_at=<Date2008-05-16.04:46:44.858>labels= ['type-bug', 'library', 'release-blocker']
title='Rename the thread module to _thread'updated_at=<Date2008-05-26.17:33:17.847>user='https://github.com/brettcannon'
Activity
brettcannon commentedon May 16, 2008
PEP-3108 has thread slated to be renamed _thread (along with dummy_thread
to _dummy_thread).
brettcannon commentedon May 20, 2008
Renames are only occurring in 3.0, not 2.6.
birkenfeld commentedon May 25, 2008
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?
brettcannon commentedon May 26, 2008
Yeah, it is essentially a deprecation so the warning should be there.
brettcannon commentedon May 26, 2008
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.
birkenfeld commentedon May 26, 2008
Then I suggest to do the same thing as for all the other renames,
leaving only the notice in the docs.
brettcannon commentedon May 26, 2008
On Mon, May 26, 2008 at 1:45 AM, Georg Brandl <report@bugs.python.org> wrote:
Works for me.