Message143367
Matthew Barnett wrote:
> Matthew Barnett <python@mrabarnett.plus.com> added the comment:
>
> I think I need a show of hands.
>
> Should the default be old behaviour (like re) or new behaviour? (It might be old now, new later.)
>
> Should there be a NEW flag (as at present), or an OLD flag, or a VERSION parameter (0=old, 1=new, 2=?)?
I prefer Antoine's suggested spelling, COMPAT, rather than OLD.
How would you write the various options? After the transition is easy:
# Get backwards-compatible behaviour:
compile(string, COMPAT)
compile(string, VERSION0)
# Get regex non-compatible behaviour:
compile(string) # will be the default in the future
compile(string, VERSION1)
But what about during the transition, when backwards-compatible
behaviour is the default? There needs to be a way to turn compatibility
mode off, not just turn it on.
# Get backwards-compatible behaviour:
compile(string) # will be the default for a release or two
compile(string, COMPAT)
compile(string, VERSION0)
# Get regex non-compatible behaviour:
compile(string, VERSION1)
So I guess my preference is VERSION0 and VERSION1 flags, even if there
is never going to be a VERSION2. |
|
Date |
User |
Action |
Args |
2011-09-02 02:13:11 | steven.daprano | set | recipients:
+ steven.daprano, loewis, georg.brandl, gregory.p.smith, jimjjewett, sjmachin, amaury.forgeotdarc, belopolsky, pitrou, nneonneo, giampaolo.rodola, rsc, timehorse, mark, vbr, ezio.melotti, mrabarnett, jaylogan, akitada, moreati, alex, r.david.murray, jacques, zdwiel, jhalcrow, stiv, davide.rizzo, ronnix, eric.snow, akoumjian |
2011-09-02 02:13:10 | steven.daprano | link | issue2636 messages |
2011-09-02 02:13:10 | steven.daprano | create | |
|