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 collinwinter
Recipients brett.cannon, collinwinter, jyasskin, pitrou
Date 2009-02-24.22:54:40
SpamBayes Score 8.590866e-09
Marked as misclassified No
Message-id <1235516116.64.0.427185955219.issue5362@psf.upfronthosting.co.za>
In-reply-to
Content
The attached patch adds a --with-py3k-warnings option to configure.
Passing --without-py3k-warnings disables all Py3k compatibility warnings
(the default is to keep the warnings). For production deployments where
performance is more important than warnings no-one will see, this can
provide a useful performance improvement:

2to3 (translate 2to3's source tree five times):
Min: 22.406 -> 22.114: 1.32% faster
Avg: 22.439 -> 22.158: 1.27% faster

Django (render a 150x150 table 100 times):
Min: 0.595 -> 0.586: 1.58% faster
Avg: 0.598 -> 0.588: 1.76% faster

Spitfire (render a 1000x1000 table 100 times):
Min: 0.752 -> 0.743: 1.29% faster
Avg: 0.754 -> 0.745: 1.25% faster

Unpickle (unpickling a list of 8000 dicts 100 times):
Min: 0.305 -> 0.301: 1.41% faster
Avg: 0.307 -> 0.302: 1.49% faster

Build env: gcc 4.3.1 x86_64 on Linux 2.6.18 (Core2 Duo)
History
Date User Action Args
2009-02-24 22:55:16collinwintersetrecipients: + collinwinter, brett.cannon, pitrou, jyasskin
2009-02-24 22:55:16collinwintersetmessageid: <1235516116.64.0.427185955219.issue5362@psf.upfronthosting.co.za>
2009-02-24 22:54:42collinwinterlinkissue5362 messages
2009-02-24 22:54:41collinwintercreate