On Monday 28 November, Guido van Rossum wrote:
> On 11/24/05, Duncan Grisby <[EMAIL PROTECTED]> wrote:
> > I have encountered a problem with the re module. I have a
> > multi-threaded program that does lots of regular expression searching,
> > with some relatively complex regular expressions. Occ
Hi all,
I've implemented a patch, please visit bug 1366311 for details.
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1366311&group_id=5470
This patch only release the GIL when the engine perform a low level
search *and* if the object searched is a string or a unicode string.
Th
Martin v. Löwis wrote:
> Formally: no; it access a Python string/Python unicode object all
> the time.
>
> Now, since all the shared objects it accesses are immutable, likely
> no harm would be done releasing the GIL. I think SRE was originally
> also intended to operate on array.array objects; th
Duncan Grisby wrote:
> Is there any fundamental reason why the re module cannot release the
> interpreter lock, for at least some of the time it is running? The
> ideal situation for me would be if it could do most of its work with
> the lock released, since the software is running on a multi proc
