This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Problem with multiprocessing module from Python
- From: Jean-Pierre Flori <jpflori at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 31 Oct 2013 18:27:39 +0000 (UTC)
- Subject: Re: Problem with multiprocessing module from Python
- Authentication-results: sourceware.org; auth=none
- References: <CAHhGz88t8H_xQ6h-a6-aQrMf+wTOVT6gMnx42tMpjs=3=qGVTQ at mail dot gmail dot com> <l4ei86$cos$2 at ger dot gmane dot org> <l4p2uq$ps8$1 at ger dot gmane dot org> <l4p6h3$801$1 at ger dot gmane dot org> <20131029205935 dot GC392 at ednor dot casa dot cgf dot cx> <l4p8oi$24u$1 at ger dot gmane dot org> <l4p8vj$24u$3 at ger dot gmane dot org> <20131030093313 dot GA28558 at calimero dot vinschen dot de>
Le Wed, 30 Oct 2013 10:33:13 +0100, Corinna Vinschen a ÃcritÂ:
> On Oct 29 21:22, Jean-Pierre Flori wrote:
>> Le Tue, 29 Oct 2013 21:19:14 +0000, Jean-Pierre Flori a ÃcritÂ:
>>
>> > Le Tue, 29 Oct 2013 16:59:35 -0400, Christopher Faylor a ÃcritÂ:
>> >> If you want this fixed, the easiest way to get that to happen is to
>> >> post a simple test case which reproduces the problem. That is not
>> >> the code snippet that you sent. A real working example would be
>> >> required.
>> > Sorry about that.
>> >
>> > Here you go:
>> > """
>> > from multiprocessing import Pool
>> >
>> > def f(x): return x
>> >
>> > p = pool(2)
>> >
>> > p.map(f, [1, 2])
>> > """
>> And I managed to introduce a typo. The third line should read Pool, so
>> it is:
>> """
>> from multiprocessing import Pool
>>
>> def f(x): return x
>>
>> p = Pool(2)
>>
>> p.map(f, [1, 2])
>> """
>
> Works for me. I guess. At least, if I run the script, nothing happens:
>
> $ python x.py $
>
> Same on 32 and 64 bit Cygwin.
>
>
> Corinna
I think I got to the bottom of this.
It seems the new implem of sem_getvalue in cgwin1.dll is the cause, see:
http://cygwin.com/ml/cygwin-patches/2013-q3/msg00006.html
It may also explain the random reproducibility if sval stays uninitialized
or something like that (I did not check it is the case though).
Reverting to 1.7.20 solved the issue on the install I tested.
I guess my previous attempts to downgrade cygwin1.dll were just badly
done:
I just decompressed the cygwin tarball which only overwrote the dll in /
usr/bin but not in /bin.
Is there a canonical way to do that in a proper way?
Putting it in a local directory and pointing setup.exe ot it?
Best,
JP
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple