This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients gvanrossum, rpointel, vstinner
Date 2014-02-17.23:42:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1392680574.83.0.750264153214.issue20666@psf.upfronthosting.co.za>
In-reply-to
Content
On old FreeBSD versions and on the latest OpenBSD (5.4), the multiprocessing module is not available because POSIX semaphores are not supported by the OS. See issues #5725 and #10348 to use SysV semaphores. #10348 was closed because "implementing SysV semaphores would be a step backwards, plus the API is a real pain" (wrote Charles-François Natali).

Would it be possible to make concurrent.futures dependency optional? In Trollius project (port of asyncio on Python 2), I implemented a very simple synchronous executor used by default as a fallback when concurrent.futures is not available (Trollius uses futures, backport of concurrent.futures for Python 2).

Attached patch is the synchronous executor adapted again on asyncio.

asyncio.executor.Future (when concurrent.futures is missing) is the simplest class and has a different API than concurrent.futures.Future. It is directly created with known result (value or exeption).
History
Date User Action Args
2014-02-17 23:42:54vstinnersetrecipients: + vstinner, gvanrossum, rpointel
2014-02-17 23:42:54vstinnersetmessageid: <1392680574.83.0.750264153214.issue20666@psf.upfronthosting.co.za>
2014-02-17 23:42:54vstinnerlinkissue20666 messages
2014-02-17 23:42:54vstinnercreate