Stefan Krah stefan-use...@bytereef.org added the comment:
I cannot reproduce this on Lucid with:
$ uname -r
2.6.32-28-generic
Isn't this an Ubuntu problem if sem_open only works with some
specific kernels?
--
nosy: +skrah
___
Python tracker
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8326
___
___
Python-bugs-list mailing list
Buck Golemon buck.gole...@amd.com added the comment:
Isn't this an Ubuntu problem if sem_open only works with some specific
kernels?
sem_open works fine (python2.6 is using it), but the python2.7 build process
didn't detect it properly. This is either a bug with Ubuntu's python2.7 build
Buck Golemon buck.gole...@amd.com added the comment:
On Ubuntu 10.10 (maverick), python2.6 is functioning correctly, but python2.7
is giving this error again.
$ /usr/bin/python2.7
from multiprocessing.synchronize import Semaphore
ImportError: This platform lacks a functioning sem_open
Mark Dickinson dicki...@gmail.com added the comment:
As an aside, I don't really understand why the sem_open check is failing on the
build machine. 'man sem_overview' says:
On a system with Linux 2.6 and a glibc that provides the NPTL threading
implementation, a complete implementation of
Matthias Klose d...@debian.org added the comment:
this was caused by r76567, introduction of the sem_open configure checks. The
build machines building the binary packages for lucid use kernels from the last
stable LTS release:
./a.out; echo $?
sem_open: Function not implemented
1
$ uname -r
Changes by R. David Murray rdmur...@bitdance.com:
--
nosy: +jnoller
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8326
___
___
Python-bugs-list
David Coconut coco...@redbrick.dcu.ie added the comment:
Issue 3770 is not relevant because this code works in Python 2.6 on both
machines (x86 and x86-64). These machines run plenty of other concurrent
processes also, which would imply to me that sem_open() does work.
I could be completely
R. David Murray rdmur...@bitdance.com added the comment:
I guess I wasn't clear. The error you are seeing is exactly the error that
issue 3770 talks about. The *build* process wasn't able to find a functioning
sem_open implementation, and therefore you see that error. Now, clearly your
R. David Murray rdmur...@bitdance.com added the comment:
I'm guessing Matthias might have some insight into this on the Ubuntu side. so
I'm adding him as nosy. I'm thinking this isn't a Python problem, but I could
be wrong.
--
nosy: +doko
title: Cannot import name SemLock - Cannot
10 matches
Mail list logo