From: Vitaly Kuznetsov <vitty@altlinux.ru>
To: <devel@lists.altlinux.org>
Subject: Re: [devel] [python] sem_open in multiprocessing.queues.Queue
Date: Thu, 19 Apr 2012 13:01:32 +0400
Message-ID: <62709ae8167159ed41c780eb501f1387@hadoop.ru> (raw)
In-Reply-To: <1334817125.12204.7@ildar.innovations.kz>
On Thu, 19 Apr 2012 12:32:05 +0600, Ildar Mulyukov wrote:
> Оба наших питона выдают следующее:
> $ python3 -c 'from multiprocessing.queues import Queue;'
> Traceback (most recent call last):
> File "/usr/lib64/python3.2/multiprocessing/synchronize.py", line
> 54,
> in <module>
> from _multiprocessing import SemLock
> ImportError: cannot import name SemLock
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
> File "<string>", line 1, in <module>
> File "/usr/lib64/python3.2/multiprocessing/queues.py", line 48, in
> <module>
> from multiprocessing.synchronize import Lock, BoundedSemaphore,
> Semaphore, Condition
> File "/usr/lib64/python3.2/multiprocessing/synchronize.py", line
> 59,
> in <module>
> " function, see issue 3770.")
> ImportError: This platform lacks a functioning sem_open
> implementation,
> therefore, the required synchronization primitives needed will not
> function, see issue 3770.
Это баг, при сборке в нашей сборочнице не проходит тест sem_open:
к примеру,
http://git.altlinux.org/tasks/archive/done/_67/69340/build/100/x86_64/log:
checking whether POSIX semaphores are enabled... no
checking for broken sem_getvalue... yes
сейчас попробую посмотреть как объехать.
next prev parent reply other threads:[~2012-04-19 9:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 6:32 Ildar Mulyukov
2012-04-19 6:45 ` REAL
2012-04-19 6:59 ` Ildar Mulyukov
2012-04-19 9:01 ` Vitaly Kuznetsov [this message]
2012-04-19 9:04 ` Ildar Mulyukov
2012-04-19 9:24 ` Vitaly Kuznetsov
2012-04-19 9:57 ` Ildar Mulyukov
2012-04-19 13:07 ` Vitaly Kuznetsov
2012-04-19 13:11 ` Aleksey Novodvorsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=62709ae8167159ed41c780eb501f1387@hadoop.ru \
--to=vitty@altlinux.ru \
--cc=devel@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git