Barry Warsaw wrote: > On Fri, 2006-01-20 at 21:43 +0100, Thomas Wouters wrote: > >> I don't believe this belongs in 2.4, since it can, actually, break code. >> Code that depends on the current situation, _TestCase__attributename. >> Fragile code, to be sure, but still. If there were a compelling reason to >> backport, I guess it could be hacked to work right-ish, but subclassing >> TestCase in this way, while convenient, isn't important enough to warrant >> this (IMHO). > > Exactly right. You're right. Next time I'm going to decide in favor of not backporting. I reverted both checkins, this and the urlparse one. For 2.5, this would be a good opportunity to add additional schemes to urlparse. Candidates? Georg
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