Message 174771 - Python tracker

➜

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	mark.dickinson
Recipients	Paul.Upchurch, eric.araujo, hynek, mark.dickinson, ned.deily, serhiy.storchaka
Date	2012-11-04.10:19:24
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
> Now benchmarks and special casing for Py_ssize_t values needed. I thought about that, but I don't think it's worth it. I did some quick timings, and as expected the new version of slice.indices is somewhat slower than the original. But I think adding a special case for Py_ssize_t values would be premature optimization.

> Now benchmarks and special casing for Py_ssize_t values needed.

I thought about that, but I don't think it's worth it.  I did some quick timings, and as expected the new version of slice.indices is somewhat slower than the original.  But I think adding a special case for Py_ssize_t values would be premature optimization.

History
Date	User	Action	Args
2012-11-04 10:19:24	mark.dickinson	set	recipients: + mark.dickinson, ned.deily, eric.araujo, hynek, Paul.Upchurch, serhiy.storchaka
2012-11-04 10:19:24	mark.dickinson	set	messageid: <[email protected]>
2012-11-04 10:19:24	mark.dickinson	link	issue14794 messages
2012-11-04 10:19:24	mark.dickinson	create