➜

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 vstinner
Recipients ethan.furman, gregory.p.smith, gvanrossum, ned.deily, python-dev, serhiy.storchaka, terry.reedy, vinay.sajip, vstinner, wolma
Date 2016-11-09.09:05:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwbH6-tuVMRYzFcR2zLLwTwqrA8Z5asj_OeWNN8=XqacZg@mail.gmail.com>
In-reply-to <CAP7+vJKiGwT3r6YeBrzM=8JqJY7L9B6kkUfjvXMay0p+h8azLw@mail.gmail.com>
Content 
About the re module, there is still a regression on the performance of
the import time: see my msg280271.

We may also revert the changeset 88110cfbf4dc (issue #28193) if we
want to keep "import re" as fast as Python 3.5.

The question is if we consider that the re module is part of the
Python core modules which must be blasing fast to import.
History
Date User Action Args
2016-11-09 09:05:18vstinnersetrecipients: + vstinner, gvanrossum, terry.reedy, gregory.p.smith, vinay.sajip, ned.deily, ethan.furman, python-dev, serhiy.storchaka, wolma
2016-11-09 09:05:18vstinnerlinkissue28637 messages
2016-11-09 09:05:18vstinnercreate