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 ezio.melotti
Recipients akitada, akoumjian, alex, amaury.forgeotdarc, belopolsky, davide.rizzo, eric.snow, ezio.melotti, georg.brandl, giampaolo.rodola, gregory.p.smith, jacques, jaylogan, jhalcrow, jimjjewett, loewis, mark, moreati, mrabarnett, nneonneo, pitrou, r.david.murray, ronnix, rsc, sjmachin, steven.daprano, stiv, timehorse, vbr, zdwiel
Date 2011-09-02.01:30:31
SpamBayes Score 1.33247e-06
Marked as misclassified No
Message-id <>
In order to replace the re module, regex must have the same behavior (except for bugs, where the correct behavior is most likely preferred, even if it's different).

Having re.OLD and warnings active by default in 3.3 (and possibly 3.4) should give enough time to fix the regex if/when necessary (either by changing the regex or by adding the re.OLD flag manually).  In 3.4 (or 3.5) we can then change the default behavior to the new semantics.

In this way we won't have to keep using the re.NEW flag on every regex.  I'm not sure if a version flag is useful, unless you are planning to add more incompatible changes.  Also each new version *flag* means one more path to add/maintain in the code.  Having a simple .regex_version attribute might be a more practical (albeit less powerful) solution.
Date User Action Args
2011-09-02 01:30:33ezio.melottisetrecipients: + ezio.melotti, loewis, georg.brandl, gregory.p.smith, jimjjewett, sjmachin, amaury.forgeotdarc, belopolsky, pitrou, nneonneo, giampaolo.rodola, rsc, timehorse, mark, vbr, mrabarnett, jaylogan, akitada, moreati, steven.daprano, alex, r.david.murray, jacques, zdwiel, jhalcrow, stiv, davide.rizzo, ronnix, eric.snow, akoumjian
2011-09-02 01:30:32ezio.melottisetmessageid: <>
2011-09-02 01:30:31ezio.melottilinkissue2636 messages
2011-09-02 01:30:31ezio.melotticreate