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 tim.peters
Recipients Arfrever, eli.bendersky, ezio.melotti, larry, mrabarnett, pitrou, python-dev, serhiy.storchaka, tim.peters
Date 2013-08-04.23:54:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Python's current regex engine isn't so coded. That's
> the reason for the up-front check.

It's peculiar then that nobody noticed before now that the check was so badly broken ;-)

Offhand, do you have an example that displays bad behavior in 2.7?  I'm curious because I didn't find one after half an hour of trying.
Date User Action Args
2013-08-04 23:54:31tim.peterssetrecipients: + tim.peters, pitrou, larry, ezio.melotti, mrabarnett, Arfrever, eli.bendersky, python-dev, serhiy.storchaka
2013-08-04 23:54:31tim.peterssetmessageid: <>
2013-08-04 23:54:31tim.peterslinkissue18647 messages
2013-08-04 23:54:31tim.peterscreate