Re: [Python-Dev] [Python-3000-checkins] r64217 - in python/branches/py3k/Lib: bsddb/test/test_associate.py bsddb/test/test_join.py bsddb/test/test_lock.py bsddb/test/test_thread.py idlelib/rpc.py idlelib/run.py socketserver.py test/test_threadedtempfile.py thread
It's water under the bridge now, but IMO it was too rash to *remove*
the old threading API from Py3k, and doubly rash to do so one day
before the beta release. Running up to a release (whether alpha, beta
or final) we should practice extra restraint, not rush to get things
in right before the deadline. Let's all be more careful the rest of
this release cycle! (I think it wasn't just Benjamin who raced to get
things in...)
--Guido
On Thu, Jun 12, 2008 at 7:00 PM, benjamin.peterson
Author: benjamin.peterson Date: Fri Jun 13 04:00:47 2008 New Revision: 64217
Log: fix more threading API related bugs
Modified: python/branches/py3k/Lib/bsddb/test/test_associate.py python/branches/py3k/Lib/bsddb/test/test_join.py python/branches/py3k/Lib/bsddb/test/test_lock.py python/branches/py3k/Lib/bsddb/test/test_thread.py python/branches/py3k/Lib/idlelib/rpc.py python/branches/py3k/Lib/idlelib/run.py python/branches/py3k/Lib/socketserver.py python/branches/py3k/Lib/test/test_threadedtempfile.py python/branches/py3k/Lib/threading.py
Modified: python/branches/py3k/Lib/bsddb/test/test_associate.py ============================================================================== --- python/branches/py3k/Lib/bsddb/test/test_associate.py (original) +++ python/branches/py3k/Lib/bsddb/test/test_associate.py Fri Jun 13 04:00:47 2008 @@ -9,7 +9,7 @@ from pprint import pprint
try: - from threading import Thread, currentThread + from threading import Thread, current_thread have_threads = 1 except ImportError: have_threads = 0
[etc.] -- --Guido van Rossum (home page: http://www.python.org/~guido/)
Guido van Rossum wrote:
It's water under the bridge now, but IMO it was too rash to *remove* the old threading API from Py3k, and doubly rash to do so one day before the beta release. Running up to a release (whether alpha, beta or final) we should practice extra restraint, not rush to get things in right before the deadline. Let's all be more careful the rest of this release cycle! (I think it wasn't just Benjamin who raced to get things in...)
Well, it wouldn't be "adding a new feature" to reinstate the old API for beta two, would it, as long as we retain the new one too? It does seem that change was a little precipitate. regards Steve -- Steve Holden +1 571 484 6266 +1 800 494 3119 Holden Web LLC http://www.holdenweb.com/
Steve Holden wrote:
Guido van Rossum wrote:
It's water under the bridge now, but IMO it was too rash to *remove* the old threading API from Py3k, and doubly rash to do so one day before the beta release. Running up to a release (whether alpha, beta or final) we should practice extra restraint, not rush to get things in right before the deadline. Let's all be more careful the rest of this release cycle! (I think it wasn't just Benjamin who raced to get things in...)
Well, it wouldn't be "adding a new feature" to reinstate the old API for beta two, would it, as long as we retain the new one too? It does seem that change was a little precipitate.
Although if we weren't actually planning on removing the old API in 3.0, I'm a little confused as to why we were adding Py3k warnings to it in 2.6... Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia --------------------------------------------------------------- http://www.boredomandlaziness.org
participants (3)
-
Guido van Rossum -
Nick Coghlan -
Steve Holden