A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2000-September/009332.html below:

[Python-Dev] Unexpected rexec behavior due to _sre

[Python-Dev] Unexpected rexec behavior due to _sre [Python-Dev] Unexpected rexec behavior due to _sreCharles G Waldman cgw@fnal.gov
Tue, 12 Sep 2000 16:57:51 -0500 (CDT)
Andrew Kuchling writes:
 > On Tue, Sep 12, 2000 at 04:48:47PM -0500, Guido van Rossum wrote:
 > >The rexec.py module needs to be fixed.  Should be simple enough.
 > >There may be other modules that it should allow too!
 > 
 > Are we sure that it's not possible to engineer segfaults or other
 > nastiness by deliberately feeding _sre bad data?  This was my primary
 > reason for not exposing the PCRE bytecode interface, since it would
 > have been difficult to make the code robust against hostile bytecodes.

If it used to be OK to "import re" in restricted mode, and now it
isn't, then this is an incompatible change and needs to be documented.
There are people running webservers and stuff who are counting on
being able to use the re module in restricted mode.




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