Right. This *definitely* is a feature, not a bug. On 1/20/06, Thomas Wouters <thomas at xs4all.net> wrote: > On Fri, Jan 20, 2006 at 06:55:03PM +0100, georg.brandl wrote: > > Author: georg.brandl > > Date: Fri Jan 20 18:55:02 2006 > > New Revision: 42116 > > > > Modified: > > python/branches/release24-maint/Lib/unittest.py > > Log: > > Patch #1388073: Make unittest.TestCase easier to subclass > > 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). > > -- > Thomas Wouters <thomas at xs4all.net> > > Hi! I'm a .signature virus! copy me into your .signature file to help me spread! > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (home page: http://www.python.org/~guido/)
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