Can anybody else reproduce this? If so, let's try find out what
OS/versions/hardware you have in common.
On Friday, 14 March 2014 11:18:28 UTC-5, Leonel Câmara wrote:
>
> > must be computed before debug() gets called, so no problem there either.
>
> Yes Jonathan but debug, or anything else, didn't need the result of the x
> computation. So it was possible, I don't know the internals of cpython that
> well, the loop was optimized away in the command line version.
>
> I also disagree that using time is not a problem. It totally is. Id like
> to see this done using timeit and much more than 5000 iterations.
>
> [edit]
>
> Also what happens if you change the web2py version to:
>
> def test():
> t = time.time
> start = t()
> x = 0.0
> for i in range(1,5000):
> x += (float(i+10)*(i+25)+175.0)/3.14
> debug("elapsed time: "+str(t()-start))
> return
>
>
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
