[Stackless] Keyword args problem with class inherited from stackless channel

Christian Tismer tismer at stackless.com
Mon Jul 16 21:46:58 CEST 2007

On 16.07.2007, at 15:42, Richard Tew wrote:

> Hi Christian,
> Just a small thing which I meant to run past you at some point.  Is
> there any reason that __new__ in the Stackless channel implementation
> is checking the arguments and erroring if there are any?  I would just
> go ahead and remove the check, but I can't help but wonder if there is
> some special problem which arises if it is removed.  Can't hurt to
> check with you in any case! :-)

This is for the same reason why int or str do not accept additional
arguments - I don't know exactly, but I followed the implicit standard
for builtin types to check their arguments exactly.
It would be easy to change, if there is a reason that deviates
enough from common practice for builtin types. Otherwise I would
prefer to stick with it. It might also help me to decide if someone
could tell me *why* builtin types are so restrictive with __new__.

(including the list for this question)

cheers - chris
Christian Tismer             :^)   <mailto:tismer at stackless.com>
tismerysoft GmbH             :     Have a break! Take a ride on Python's
Johannes-Niemeyer-Weg 9A     :    *Starship* http://starship.python.net/
14109 Berlin                 :     PGP key -> http://wwwkeys.pgp.net/
work +49 30 802 86 56  mobile +49 173 24 18 776  fax +49 30 80 90 57 05
PGP 0x57F3BF04       9064 F4E1 D754 C2FF 1619  305B C09C 5A3B 57F3 BF04
       whom do you want to sponsor today?   http://www.stackless.com/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.stackless.com/pipermail/stackless/attachments/20070716/6c5825eb/attachment.htm>
-------------- next part --------------
Stackless mailing list
Stackless at stackless.com

More information about the Stackless mailing list