Guido van Rossum wrote: > > > There was talk about changing string (the base class) to something > > else since it was the same name as the module. Was there ever a > > decision made? > > Oops, no. Let's call it basestring. Can you do that? Will do. > > But this is not what I would expect: > > > > >>> import string > > >>> class newstr(string): pass > > ... > > # i would have expected this to raise a TypeError > > >>> x = newstr() > > Traceback (most recent call last): > > File "<stdin>", line 1, in ? > > TypeError: 'module' object is not callable > > > > Perhaps this error should be handled when the class is constructed > > rather than when instantiating an object? > > Can you submit a SF bug report for this? It has nothing to do with > string per se -- the bug is that you can use any module as a base > class. :-( Will do. Neal
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