Regexp syntax change in 1.6?

[Adam Sampson]

effbot at pythonware.com writes:

> > Well, (x?)? should be equivalent to (x)? or (x?), so
> > perhaps it's reasonable to be issued a warning. An
> > outright error seems rather harsh.

So what would it do for a warning? Raise an "sre.StupidRegexp"
exception? ;)

> It's an overambitious sanity check in SRE's code generator.
> It will be fixed in 2.0 final.

Brilliant; I'll test it when the next 2.0 appears. Thanks very much,

-- 

Adam Sampson
azz at gnu.org