[Python-Dev] Rationale for sum()'s design? (original) (raw)
Batista, Facundo FBatista at uniFON.com.ar
Tue Mar 15 16:58:51 CET 2005
- Previous message: [Python-Dev] Re: Rationale for sum()'s design?
- Next message: [Python-Dev] Rationale for sum()'s design?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[Guido van Rossum]
#- > 1. When omitting the second argument, would supplying an #- empty list return 0, #- > None or raise an exception? #- #- Good question...
I'd go for None:
Is a good default for a non-existing argument.
If won't get None from sum() in other case (unless you do sum(None), but you should be aware of that).
. Facundo
Bitácora De Vuelo: http://www.taniquetil.com.ar/plog PyAr - Python Argentina: http://pyar.decode.com.ar/
-------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20050315/58d3f3e4/attachment.htm
- Previous message: [Python-Dev] Re: Rationale for sum()'s design?
- Next message: [Python-Dev] Rationale for sum()'s design?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]