Related to my last message: should None become a keyword in Py3K? -- ?!ng
Barry A. Warsaw wrote:
"KY" == Ka-Ping Yee <ping@lfw.org> writes:
KY> Related to my last message: should None become a keyword in KY> Py3K?
Why? Just to reserve it?
to avoid stuff errors like: def foo(): result = None # two screenfuls of code None, a, b = mytuple # perlish unpacking which gives an interesting error on the first line, instead of a syntax error on the last. </F>
"KY" == Ka-Ping Yee <ping@lfw.org> writes:
KY> Related to my last message: should None become a keyword in KY> Py3K?
Barry A. Warsaw schrieb:
Why? Just to reserve it?
This is related to the general type checking discussion. IMO the suggested >>> 1 > 0 True wouldn't buy us much, as long the following behaviour stays in Py3K: >>> a = '2' ; b = 3 >>> a < b 0 >>> a > b 1 This is irritating to Newcomers (at least from rather short time experience as member of python-help)! And this is esspecially irritating, since you can't do >>> c = a + b Traceback (innermost last): File "<stdin>", line 1, in ? TypeError: illegal argument type for built-in operation IMO this difference is far more difficult to catch for newcomers than the far more often discussed 5/3 == 1 behaviour. Have a nice weekend and don't forget to hunt for remaining bugs in Fred upcoming 1.5.2p2 docs ;-), Peter. -- Peter Funk, Oldenburger Str.86, D-27777 Ganderkesee, Germany, Fax:+49 4222950260 office: +49 421 20419-0 (ArtCom GmbH, Grazer Str.8, D-28359 Bremen)
participants (5)
-
Barry A. Warsaw -
Fredrik Lundh -
Guido van Rossum -
Ka-Ping Yee -
pf＠artcom-gmbh.de