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 ncoghlan
Recipients Arfrever, christian.heimes, ncoghlan, neologix, pitrou, python-dev, serhiy.storchaka, vstinner
Date 2013-11-15.13:05:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384520750.44.0.354367270173.issue19183@psf.upfronthosting.co.za>
In-reply-to
Content
I reviewed the latest PEP text at http://www.python.org/dev/peps/pep-0456/

I'm almost prepared to accept the current version of the implementation, but there's one technical decision to be clarified and a few placeholders in the PEP that need to be cleaned up prior to formal acceptance:

* The rationale for turning off the small string optimisation by default rather than setting the cutoff to 7 bytes isn't at all clear to me. A consistent 3-5% speed difference on the benchmark suite isn't trivial, and if we have the small string optimization off by default, why aren't we just deleting that code instead?

* A link to the benchmark suite at http://hg.python.org/benchmarks should be included at the appropriate places in the PEP

* The "Further things to consider" section needs to be moved to a paragraph under "Discussion" describing the current implementation (i.e. the hash equivalence is tolerated for simplicity and consistency)

* The "TBD" in the performance section needs to go. Reference should be made to the numbers in the small string optimisation section.

* The performance numbers need to be clear on what version of the feature branch was used to obtain them (preferably the one you plan to commit!).
History
Date User Action Args
2013-11-15 13:05:50ncoghlansetrecipients: + ncoghlan, pitrou, vstinner, christian.heimes, Arfrever, neologix, python-dev, serhiy.storchaka
2013-11-15 13:05:50ncoghlansetmessageid: <1384520750.44.0.354367270173.issue19183@psf.upfronthosting.co.za>
2013-11-15 13:05:50ncoghlanlinkissue19183 messages
2013-11-15 13:05:49ncoghlancreate