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-01.18:40:00
SpamBayes Score 1.69891e-06
Marked as misclassified No
Message-id <>
Changing the name of the flag is fine with me.

Having a warning for unescaped brackets that trigger set operations might also be a solution (once escaped they will still work on the old re).  Maybe the same could also be done for scoped flags.

FWIW I tried to come up with a simpler regex that makes some sense and triggers unwanted set operations and I didn't come up with anything except:
>>> regex.findall('[[(]foo[)]]', '[[foo] (foo)]')
['f', 'o', 'o', '(', 'f', 'o', 'o', ')']
>>> re.findall('[[(]foo[)]]', '[[foo] (foo)]')
(but this doesn't make too much sense).  Complex regex will still break though, so the issue needs to be addressed somehow.
Date User Action Args
2011-09-01 18:40:01ezio.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-01 18:40:00ezio.melottisetmessageid: <>
2011-09-01 18:40:00ezio.melottilinkissue2636 messages
2011-09-01 18:40:00ezio.melotticreate