Raymond Hettinger wrote:
> [Filipe Fernandes]
>> The reasons for using JoinableQueue I think are obvious. I want to
>> block the main processing using queue.join() until the tasks that have
>> been placed on the queue have been finished by the worker processes.
>>
I'm currently using the multiprocessing package and I'm hugely
impressed at its simplicity (thanks very much Jesse Noller).
Although, it seems that there's a bug in JoinableQueue's which renders
using it pointless over a regular Queue as per Issue 4660
http://bugs.python.org/issue4660
To re-iter
On Fri, Jul 4, 2008 at 8:36 AM, Peter Otten <[EMAIL PROTECTED]> wrote:
> Henning_Thornblad wrote:
>
>> What can be the cause of the large difference between re.search and
>> grep?
>
> grep uses a smarter algorithm ;)
>
>> This script takes about 5 min to run on my computer:
>> #!/usr/bin/env python
> On Jun 3, 12:34 pm, "Filipe Fernandes" <[EMAIL PROTECTED]> wrote:
>> On Tue, Jun 3, 2008 at 10:41 AM, Paul McGuire <[EMAIL PROTECTED]> wrote:
>> But I do have more questions... when reading the ply.py header (in
>> 2.5) I found the following paragra
On Tue, Jun 3, 2008 at 10:41 AM, Paul McGuire <[EMAIL PROTECTED]> wrote:
> If you learn both, you may find that pyparsing is a good way to
> quickly prototype a particular parsing problem, which you can then
> convert to PLY for performance if necessary. The pyparsing prototype
> will be an effici
I have a project that uses a proprietary format and I've been using
regex to extract information from it. I haven't hit any roadblocks
yet, but I'd like to use a parsing library rather than maintain my own
code base of complicated regex's. I've been intrigued by the parsers
available in python, w
