Showing content from http://mail.python.org/pipermail/python-dev/attachments/20110828/ea30cb1a/attachment.html below:
<br><div class="gmail_quote">On Sun, Aug 28, 2011 at 3:48 AM, Terry Reedy <span dir="ltr"><<a href="mailto:tjreedy@udel.edu">tjreedy@udel.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
These are reasons why both Ezio and I suggested on the tracker adding regex without deleting re. (I personally would not mind just replacing re with regex, but then I have no legacy re code to break. So I am not suggesting that out of respect for those who do.)<font color="#888888"></font><br>
</blockquote><div><br>I would actually prefer to replace re.<br><br>Before doing that we should make a list of all the differences between the two modules (possibly in the PEP). On the regex page on PyPI there's already a list that can be used for this purpose [0].<br>
For bug fixes it *shouldn't* be a problem if the behavior changes. New features shouldn't bring any backward-incompatible behavioral changes, and, as far as I understand, Matthew introduced the NEW flag [1], to avoid problems when they do.<br>
<br>I think re should be kept around only if there are too many incompatibilities left and if they can't be fixed in regex.<br><br>Best Regards,<br>Ezio Melotti<br><br><br>[0]: <a href="http://pypi.python.org/pypi/regex/0.1.20110717">http://pypi.python.org/pypi/regex/0.1.20110717</a><br>
[1]:Â "The NEW flag turns on the new behaviour of this module, which can differ from that of the 're' module, such as splitting on zero-width matches, inline flags affecting only what follows, and being able to turn inline flags off."</div>
</div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4