homepage

> Subclass of set can now define a __new__() method with 
> additional keyword parameters without overriding also __init__().
Is there any use case for this? Offhand, I can't think of any reason.
The new code in set.__init__ is somewhat opaque and is likely slower, so I prefer the previous code unless there is a legitimate use case being served.