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 rhettinger
Recipients barry, r.david.murray, rhettinger, serhiy.storchaka
Date 2017-09-26.16:37:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1506443822.37.0.379544681103.issue31580@psf.upfronthosting.co.za>
In-reply-to
Content
I'm flat-out opposed to changing the default behavior.  If some API change gets make it needs to strictly be opt-in.  

Even then, I don't think this is a great idea.  We already have ways to do it if people actually cared about this.

FWIW, other languages also have regex compile() and it always means compile immediate.  The proposed change alters the semantics of existing code and undermines the explicit decisions of people who wrote existing packages.  It is at odds with what re.compile() means everywhere else.

Having an opt-out IMMEDIATE flag makes it difficult for package writers to maintain code across versions.  Also flags further complicate an API that is already challenging.
History
Date User Action Args
2017-09-26 16:37:02rhettingersetrecipients: + rhettinger, barry, r.david.murray, serhiy.storchaka
2017-09-26 16:37:02rhettingersetmessageid: <1506443822.37.0.379544681103.issue31580@psf.upfronthosting.co.za>
2017-09-26 16:37:02rhettingerlinkissue31580 messages
2017-09-26 16:37:02rhettingercreate