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/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4