[Python-Dev] Issue #10348: concurrent.futures doesn't work on BSD (original) (raw)
Georg Brandl g.brandl at gmx.net
Wed Dec 29 16:01:38 CET 2010
- Previous message: [Python-Dev] Issue #10348: concurrent.futures doesn't work on BSD
- Next message: [Python-Dev] Issue #10348: concurrent.futures doesn't work on BSD
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 29.12.2010 14:17, schrieb Victor Stinner:
Hi,
FreeBSD 7.2 3.x buildbot is red since some weeks (or months?) because of a concurrent.futures failure. The problem is that testconcurrentfutures uses many (multiprocessing) POSIX semaphores, whereas POSIX semaphores support in FreeBSD is recent and limited. We have to use SysV semaphores (ftok, semget, semop, semctl, ...) instead of POSIX semaphores (semopen, semgetvalue, semunlink, ...). See: * http://bugs.python.org/issue10348 * "Too many open files" errors on "x86 FreeBSD 7.2 3.x" buildbot ^-- thread in python-dev opened last month 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.
Georg
- Previous message: [Python-Dev] Issue #10348: concurrent.futures doesn't work on BSD
- Next message: [Python-Dev] Issue #10348: concurrent.futures doesn't work on BSD
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]