A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2002-August/028097.html below:

[Python-Dev] PEP 218 (sets); moving set.py to Lib

[Python-Dev] PEP 218 (sets); moving set.py to Lib [Python-Dev] PEP 218 (sets); moving set.py to LibPaul Svensson paul-python@svensson.org
Tue, 20 Aug 2002 19:27:53 -0400 (EDT)
On Tue, 20 Aug 2002, Guido van Rossum wrote:

>> From: "Guido van Rossum" <guido@python.org>
>> > I am still perplexed that I receoved *no* feedback on the sets module
>> > except on this issue of sort order (which I consider solved by adding
>> > a method _repr() that takes an optional 'sorted' argument).
>>
>> I think the __init__() code in BaseSet should be pushed down into Set and ImmutableSet.  It should be replaced by code raising a
>> TypeError just like we do for basestring:
>>
>> >>> basestring('abc')
>> Traceback (most recent call last):
>>   File "<stdin>", line 1, in ?
>> TypeError: The basestring type cannot be instantiated
>
>Good idea.  I checked this in, raising NotImplementedError.

Is there any particular reason BaseSet and basestring need to raise different
exceptions on an attempt at instantiation ?

	/Paul




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