Message169790
Comparing the execution time with and without the int=int argument of this command:
amoura@amoura-laptop:~/cpython$ time ./python -c "from random import shuffle; lst=list(range(1000000)); shuffle(lst); print (len(lst))"
I get with int=int:
real 0m13.755s
user 0m13.777s
sys 0m0.124s
and without it:
real 0m13.876s
user 0m13.701s
sys 0m0.116s
So it makes no difference in practice. On the other hand, removing this has a chance of braking existing code, if someone somewhere actually uses the third argument for something - I can't image what, but still... |
|
Date |
User |
Action |
Args |
2012-09-03 18:06:24 | eng793 | set | recipients:
+ eng793, rhettinger, r.david.murray, serhiy.storchaka |
2012-09-03 18:06:24 | eng793 | set | messageid: <1346695584.84.0.846309894773.issue15837@psf.upfronthosting.co.za> |
2012-09-03 18:06:24 | eng793 | link | issue15837 messages |
2012-09-03 18:06:23 | eng793 | create | |
|