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

Jesse Noller jnoller at gmail.com
Wed Dec 29 18:54:57 CET 2010

On Wed, Dec 29, 2010 at 10:28 AM, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>>> I would like to know if it should be considered as a release blocker.
>>> Georg Brandl said yes on IRC.
>> Under the condition that it is within reason to fix it before the
>> release.
> What *should* be possible is to disable building
> SemLock/multiprocessing.synchronize on FreeBSD. As a consequence,
> multiprocessing locks would stop working on FreeBSD, and concurrent
> futures; the tests would recognize this lack of features and get
> skipped.
> Regards,
> Martin

The multiprocessing test suite already skips the tests which use the
(broken) functionality on BSD correctly. This logic needs to be added
to the concurrent.futures library.


More information about the Python-Dev mailing list