[Python-Dev] Issue #10348: concurrent.futures doesn't work on BSD

Antoine Pitrou solipsis at pitrou.net
Wed Dec 29 23:33:17 CET 2010

On Wed, 29 Dec 2010 23:24:32 +0100
"Martin v. Löwis" <martin at v.loewis.de> wrote:
> > I don't have a good suggestion (or a computer with a keyboard
> > anywhere near me) right now, but making a migration/fallback to SYSV
> > style semaphores a release blocker seems like a mistake to me.
> And indeed, I don't propose to make that a release blocker. Instead,
> I propose to disable support for the module (either multiprocessing
> or concurrent.futures only) on FreeBSD, and make such disabling a
> release blocker.

I don't really agree with this. There's no need to explicitly forbid
use of multiprocessing from FreeBSD. First, it is not our task to
validate that each and every OS conforms to the APIs it claims to
implement. Second, such disabling would make life uselessly more
complicated for users the day FreeBSD actually fixes their stuff.

So, IMO, skipping tests is enough. At worse, multiprocessing can issue
a warning when imported under these OSes.



More information about the Python-Dev mailing list