[issue8326] Cannot import name SemLock on Ubuntu lucid

Buck Golemon 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 configuration, or wit

[issue8326] Cannot import name SemLock on Ubuntu lucid

Changes by Antoine Pitrou : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue8326] Cannot import name SemLock on Ubuntu lucid

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

[issue8326] Cannot import name SemLock on Ubuntu lucid

Buck Golemon 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 implementation, therefo

[issue8326] Cannot import name SemLock on Ubuntu lucid

Mark Dickinson 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 POSIX semaphores is

[issue8326] Cannot import name SemLock on Ubuntu lucid

Changes by R. David Murray : -- nosy: +jnoller ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue8326] Cannot import name SemLock on Ubuntu lucid

Matthias Klose 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 2.6.24-25-server

[issue8326] Cannot import name SemLock on Ubuntu lucid

R. David Murray 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 platform does have a func

[issue8326] Cannot import name SemLock on Ubuntu lucid

David Coconut 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 wrong as I'm no expert on

[issue8326] Cannot import name SemLock on Ubuntu lucid

R. David Murray 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 import name SemLock on