This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eng793
Recipients eng793, r.david.murray, rhettinger, serhiy.storchaka
Date 2012-09-03.18:06:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1346695584.84.0.846309894773.issue15837@psf.upfronthosting.co.za>
In-reply-to
Content
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...
History
Date User Action Args
2012-09-03 18:06:24eng793setrecipients: + eng793, rhettinger, r.david.murray, serhiy.storchaka
2012-09-03 18:06:24eng793setmessageid: <1346695584.84.0.846309894773.issue15837@psf.upfronthosting.co.za>
2012-09-03 18:06:24eng793linkissue15837 messages
2012-09-03 18:06:23eng793create