Closed GoogleCodeExporter closed 9 years ago
How it should behave is a bit of a grey area.
The re module says 'x' and '|t|e|s|t|'.
Perl and PCRE says 'xx' and '|||||||||'.
This is because .* and .*? can/could match 0 characters after matching the >0
characters, and there are cases where the re module definitely gets it wrong,
so it's not clear whether the re module is getting it right here.
Original comment by re...@mrabarnett.plus.com
on 30 Jan 2014 at 3:03
Hmm well I dont really have an opinion. The behavior of re seems intuitively
correct to me, but then that may just be because I have been using re for
years.
I just thought I'd report the discrepancy, as one of the goals of regex is (as
I understand it) to replace re as seamlessly as possible.
Original comment by adse...@calibre-ebook.com
on 30 Jan 2014 at 3:09
Fixed in regex 2014.01.30.
It now behaves more like the re module in the version 0 behaviour.
Original comment by re...@mrabarnett.plus.com
on 30 Jan 2014 at 9:36
Original issue reported on code.google.com by
adse...@calibre-ebook.com
on 30 Jan 2014 at 1:28