On Mon, Aug 31, 2009 at 5:01 PM, Greg Ewing <span dir="ltr"><<a href="mailto:greg.ewing@canterbury.ac.nz">greg.ewing@canterbury.ac.nz</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Antoine Pitrou wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Did your coworker run any timings instead of basing his assumptions on bytecode<br>
size?<br>
</blockquote>
<br></div>
In any case, what are you suggesting -- that the last value<br>
returned by a function call in the body should be the<br>
default return value?<br>
<br>
I don't think the unpredictability that would introduce<br>
would be a good idea.<br></blockquote><div><br></div><div>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.</div><div><br></div><div>
This is pretty fundamental to the Python API.</div><div><br></div><div>-jake </div></div>