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 steve.newcomb
Recipients rhettinger, serhiy.storchaka, steve.newcomb
Date 2016-08-31.15:15:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <43375310-4d61-3c52-8fa7-22bd0d8138c0@coolheads.com>
In-reply-to <722ff06a-9b68-4ef6-e76a-d81e3e581577@coolheads.com>
Content
Having disabled multiprocessing, I ran new, more extensive profiles.  
The biggest problem is in re.sub(), which in our codebase evidently uses 
3 times as much processing time in Python 2.7.12 as it does in Python 2.7.6.

I'm attaching the profile reports for both runs.

Here's a possibly-relevant question: Are regular expressions now being 
unnecessarily recompiled by re.sub()?

We never call the sub() method of a compiled regular expression; we 
always call sub() as "re.sub()" and pass the compiled regular expression 
as the first argument.  Years ago when our code was first developed, 
re.sub() did not always work correctly when invoked as a method of a 
compiled regular expression object.  I don't know if that's still a 
problem, but the problem persisted for years, and so we have a 
convention of always invoking sub() at the module level.

Steve Newcomb
Files
File name Uploaded
newcomb_profile_report_for_2.7.12.txt steve.newcomb, 2016-08-31.15:15:03
newcomb_profile_report_for_2.7.6.txt steve.newcomb, 2016-08-31.15:14:51
History
Date User Action Args
2016-08-31 15:15:18steve.newcombsetrecipients: + steve.newcomb, rhettinger, serhiy.storchaka
2016-08-31 15:15:16steve.newcomblinkissue27898 messages
2016-08-31 15:15:16steve.newcombcreate