Baptiste Lepilleur <baptiste.lepilleur <at> gmail.com> writes: > > I've tried, but there is no change in result (the regexp does not use \w & > co but specify a lot unicode ranges). All strings are already of unicode > type in 2.6. No they aren't. You should add "from __future__ import unicode_literals" at the start of your script and run it again. > Hmmm, I was confusing with other modules (bzip2 & hashlib?). Looking back at > the result of your benchmark it's obvious. Is there a place where the list of > functions releasing the GIL is available? I did not see anything in > bz2.compress documentation. No, there isn't. You'd have to test, or read the source code. But bz2 and zlib, for example, do release the GIL. Regards Antoine.
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