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 serhiy.storchaka
Recipients BreamoreBoy, Devin Jeanpierre, 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, mattchaput, moreati, mrabarnett, ncoghlan, nneonneo, pitrou, r.david.murray, ronnix, rsc, sandro.tosi, serhiy.storchaka, sjmachin, steven.daprano, stiv, timehorse, tshepang, vbr, zdwiel
Date 2014-11-08.20:22:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <16272277.6LCEqyUnHx@raxxla>
In-reply-to <>
> So you are suggesting to fix bugs in re to make it closer to regex, and then
> replace re with a forked subset of regex that doesn't include advanced
> features, or just to fix/improve re until it matches the behavior of regex?

Depends on what will be easier. May be some bugs are so hard to fix that 
replacing re with regex is only solution. But if fixed re will be simpler and 
faster than lightened regex and will contain all necessary features, there 
will be no need in the replacing. Currently the code of regex looks more high 
level and better structured, but the code of re looks simpler and is much 
smaller. In any case the closer will be re and regex the easier will be the 
Date User Action Args
2014-11-08 20:22:10serhiy.storchakasetrecipients: + serhiy.storchaka, loewis, georg.brandl, gregory.p.smith, jimjjewett, sjmachin, amaury.forgeotdarc, ncoghlan, belopolsky, pitrou, nneonneo, giampaolo.rodola, rsc, timehorse, mark, vbr, Devin Jeanpierre, ezio.melotti, mrabarnett, jaylogan, akitada, moreati, steven.daprano, alex, r.david.murray, jacques, zdwiel, sandro.tosi, BreamoreBoy, jhalcrow, stiv, davide.rizzo, mattchaput, ronnix, tshepang, eric.snow, akoumjian
2014-11-08 20:22:10serhiy.storchakalinkissue2636 messages
2014-11-08 20:22:10serhiy.storchakacreate