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 pitrou
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-01.18:18:25
SpamBayes Score 0.00013282914
Marked as misclassified No
Message-id <1314900952.3617.21.camel@localhost.localdomain>
In-reply-to <>
> Thanks for the explanation, but isn't this a backward incompatible
> feature?
> I think it should be enabled only when the re.NEW flag is passed.
> The idiom [][...] is also quite common, so I think it might break
> different programs if regex has a different behavior.

As someone said, I'd rather have a re.COMPAT flag.  re.NEW will look
silly in a few years.
Also, we can have a warning about unescaped brackets during a
transitional period. However, it really needs the warning to be enabled
by default, IMO.
Date User Action Args
2011-09-01 18:18:26pitrousetrecipients: + pitrou, loewis, georg.brandl, gregory.p.smith, jimjjewett, sjmachin, amaury.forgeotdarc, belopolsky, nneonneo, giampaolo.rodola, rsc, timehorse, mark, vbr, ezio.melotti, mrabarnett, jaylogan, akitada, moreati, steven.daprano, alex, r.david.murray, jacques, zdwiel, jhalcrow, stiv, davide.rizzo, ronnix, eric.snow, akoumjian
2011-09-01 18:18:25pitroulinkissue2636 messages
2011-09-01 18:18:25pitroucreate