Re: [Python-Dev] Autoloading? (Making Queue.Queue easier to use)
Aahz writes:
(Python 3.0 should "deprecate" ``thread`` by renaming it to ``_thread``).
Guido says:
+1. (We could even start doing this before 3.0.)
Before 3.0, let's deprecate it by listing it in the Deprecated modules section within the documentation... no need to gratuitously break code by renaming it until 3.0 arrives. -- Michael Chermside
On Wed, Oct 12, 2005, Michael Chermside wrote:
Guido says:
Aahz writes:
(Python 3.0 should "deprecate" ``thread`` by renaming it to ``_thread``).
+1. (We could even start doing this before 3.0.)
Before 3.0, let's deprecate it by listing it in the Deprecated modules section within the documentation... no need to gratuitously break code by renaming it until 3.0 arrives.
Note carefully the deprecation in quotes. It's not going to be literally deprecated, only renamed, similar to the way _socket and socket work together. We could also rename to _threading, but I prefer the simpler change of only a prepended underscore. -- Aahz (aahz@pythoncraft.com) <*> http://www.pythoncraft.com/ "If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." --Red Adair
On 10/12/05, Aahz
Note carefully the deprecation in quotes. It's not going to be literally deprecated, only renamed, similar to the way _socket and socket work together. We could also rename to _threading, but I prefer the simpler change of only a prepended underscore.
Could you specify exactly what you have in mind? How would backwards compatibility be maintained in 2.x? -- --Guido van Rossum (home page: http://www.python.org/~guido/)
On Wed, Oct 12, 2005, Guido van Rossum wrote:
On 10/12/05, Aahz
wrote: Note carefully the deprecation in quotes. It's not going to be literally deprecated, only renamed, similar to the way _socket and socket work together. We could also rename to _threading, but I prefer the simpler change of only a prepended underscore.
Could you specify exactly what you have in mind? How would backwards compatibility be maintained in 2.x?
I'm suggesting that we add a doc note that using the thread module is discouraged and that it will be renamed in 3.0. -- Aahz (aahz@pythoncraft.com) <*> http://www.pythoncraft.com/ "If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." --Red Adair
participants (3)
-
Aahz
-
Guido van Rossum
-
Michael Chermside