RetroSearch Browse

Wed Dec 29 16:28:20 CET 2010 · https://mail.python.org/pipermail/python-dev/2010-December/107091.html

>> 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

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2010-December/107091.html below:

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