Re: Python 2.6, multiprocessing module and BSD

2008-10-23 Thread MRAB
On Oct 22, 5:14 pm, Philip Semanchuk <[EMAIL PROTECTED]> wrote: > On Oct 22, 2008, at 11:37 AM, Jesse Noller wrote: > > > On Wed, Oct 22, 2008 at 11:06 AM, Philip Semanchuk <[EMAIL PROTECTED] > > > wrote: > >>> One oversight I noticed the multiprocessing module docs is that a > >> semaphore's acqui

Re: Python 2.6, multiprocessing module and BSD

2008-10-22 Thread Philip Semanchuk
On Oct 22, 2008, at 11:37 AM, Jesse Noller wrote: On Wed, Oct 22, 2008 at 11:06 AM, Philip Semanchuk <[EMAIL PROTECTED] > wrote: One oversight I noticed the multiprocessing module docs is that a semaphore's acquire() method shouldn't have a timeout on OS X as sem_timedwait() isn't supported o

Re: Python 2.6, multiprocessing module and BSD

2008-10-22 Thread Jesse Noller
On Wed, Oct 22, 2008 at 11:06 AM, Philip Semanchuk <[EMAIL PROTECTED]> wrote: >> The BSD issue was raised late in the cycle for 2.6. The problem is >> that FBSD's support is "very experimental" as Phillip points out - and >> OpenBSD doesn't even have them. >> >> Due to the lateness of the issue and

Re: Python 2.6, multiprocessing module and BSD

2008-10-22 Thread Philip Semanchuk
On Oct 22, 2008, at 10:11 AM, Jesse Noller wrote: On Tue, Oct 21, 2008 at 6:45 PM, <[EMAIL PROTECTED]> wrote: It seems that the multiprocessing module in 2.6 is broken for *BSD; I've seen issue 3770 regarding this. I'm curious if there are more details on this issue since the posts in 3770 we

Re: Python 2.6, multiprocessing module and BSD

2008-10-22 Thread Jesse Noller
On Wed, Oct 22, 2008 at 10:31 AM, <[EMAIL PROTECTED]> wrote: > On Oct 22, 8:11 am, "Jesse Noller" <[EMAIL PROTECTED]> wrote: >> On Tue, Oct 21, 2008 at 6:45 PM, <[EMAIL PROTECTED]> wrote: >> > It seems that the multiprocessing module in 2.6 is broken for *BSD; >> > I've seen issue 3770 regarding

Re: Python 2.6, multiprocessing module and BSD

2008-10-22 Thread YouCanCallMeAl
On Oct 22, 8:11 am, "Jesse Noller" <[EMAIL PROTECTED]> wrote: > On Tue, Oct 21, 2008 at 6:45 PM,  <[EMAIL PROTECTED]> wrote: > > It seems that the multiprocessing module in 2.6 is broken for *BSD; > > I've seen issue 3770 regarding this. I'm curious if there are more > > details on this issue since

Re: Python 2.6, multiprocessing module and BSD

2008-10-22 Thread YouCanCallMeAl
On Oct 21, 8:08 pm, Philip Semanchuk <[EMAIL PROTECTED]> wrote: > On Oct 21, 2008, at 6:45 PM, [EMAIL PROTECTED] wrote: > > > It seems that the multiprocessing module in 2.6 is broken for *BSD; > > I've seen issue 3770 regarding this. I'm curious if there are more > > details on this issue since th

Re: Python 2.6, multiprocessing module and BSD

2008-10-22 Thread Jesse Noller
On Tue, Oct 21, 2008 at 6:45 PM, <[EMAIL PROTECTED]> wrote: > It seems that the multiprocessing module in 2.6 is broken for *BSD; > I've seen issue 3770 regarding this. I'm curious if there are more > details on this issue since the posts in 3770 were a bit unclear. For > example, one post claimed

Re: Python 2.6, multiprocessing module and BSD

2008-10-21 Thread Philip Semanchuk
On Oct 21, 2008, at 6:45 PM, [EMAIL PROTECTED] wrote: It seems that the multiprocessing module in 2.6 is broken for *BSD; I've seen issue 3770 regarding this. I'm curious if there are more details on this issue since the posts in 3770 were a bit unclear. For example, one post claimed that the p

Python 2.6, multiprocessing module and BSD

2008-10-21 Thread YouCanCallMeAl
It seems that the multiprocessing module in 2.6 is broken for *BSD; I've seen issue 3770 regarding this. I'm curious if there are more details on this issue since the posts in 3770 were a bit unclear. For example, one post claimed that the problem was that sem_open isn't implemented in *BSD, but it