[Python-Dev] default of returning None hurts performance?
Gregory P. Smith
greg at krypto.org
Tue Sep 1 03:03:12 CEST 2009
More information about the Python-Dev mailing list
Tue Sep 1 03:03:12 CEST 2009
- Previous message: [Python-Dev] default of returning None hurts performance?
- Next message: [Python-Dev] default of returning None hurts performance?
- 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. > gads no. we're not shell or perl! don't do that :) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20090831/76aa1845/attachment.htm>
- Previous message: [Python-Dev] default of returning None hurts performance?
- Next message: [Python-Dev] default of returning None hurts performance?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list