Showing content from http://mail.python.org/pipermail/python-dev/attachments/20120603/ceccdc4c/attachment-0001.html below:
On Sun, Jun 3, 2012 at 5:21 PM, "Martin v. Löwis" <span dir="ltr"><<a href="mailto:martin@v.loewis.de" target="_blank">martin@v.loewis.de</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On the minus side, the JIT only works on x86 and x86_64, on the plus<br>
side, since it's 100% API compatible, it can be used as a _xxx<br>
speedup module relatively easy.<br>
<br>
Do people have opinions?<br>
</blockquote>
<br></div>
The main concern for re is not speed, but functionality. The Python re<br>
module needs to grow a number of features, and correct a number of bugs.<br>
So 100% compatible is actually not good enough. 95% compatible (with<br>
the features added and the bugs fixed) would be better.<br>
<br>
OTOH, sharing the re code with PyPy would be a desirable goal, as would<br>
be writing the re code in Python (although SRE already implements<br>
significant parts in Python).<br></blockquote><div><br></div><div>We did not reimplement those parts in RPython, they're still in python (so the sre engine does not accept regex, but instead the lower-level description, etc. etc.)</div>
<div>Â </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
As a speedup module, it's uninteresting - we want to simplify maintenance, not complicate it. So this can only work if it replaces<br>
SRE.<br>
<br>
Regards,<br>
Martin<br>
</blockquote></div><br>
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