[Python-Dev] default of returning None hurts performance? (original) (raw)
Jake McGuire mcguire at google.com
Tue Sep 1 18:40:17 CEST 2009
- Previous message: [Python-Dev] default of returning None hurts performance?
- Next message: [Python-Dev] why different between staticmethod and classmethod on non-callable object?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Aug 31, 2009 at 5:01 PM, Greg Ewing <greg.ewing at canterbury.ac.nz>wrote:
Antoine Pitrou wrote:
Did your coworker run any timings instead of basing his assumptions on bytecode size?
In any case, what are you suggesting -- that the last value returned by a function call in the body should be the default return value? I don't think the unpredictability that would introduce would be a good idea.
Never mind the fact that there is a lot of Python code out there that assumes that functions without an explicit return value, return None.
This is pretty fundamental to the Python API.
-jake -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20090901/114fa872/attachment.htm>
- Previous message: [Python-Dev] default of returning None hurts performance?
- Next message: [Python-Dev] why different between staticmethod and classmethod on non-callable object?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]