[issue8326] Cannot import name SemLock on Ubuntu

Barry A. Warsaw added the comment: On Apr 26, 2011, at 09:45 PM, Matthias Klose wrote: >Matthias Klose added the comment: > >> Barry A. Warsaw added the comment: >> >> I'm closing this as invalid for Python, since I believe this is strictly an >> Ubuntu bug caused by an out-of-date kernel on

[issue8326] Cannot import name SemLock on Ubuntu

Matthias Klose added the comment: > Barry A. Warsaw added the comment: > > I'm closing this as invalid for Python, since I believe this is strictly an > Ubuntu bug caused by an out-of-date kernel on the build farm. that's where I disagree. a configure check should not be dependent on the run

[issue8326] Cannot import name SemLock on Ubuntu

Barry A. Warsaw added the comment: I'm closing this as invalid for Python, since I believe this is strictly an Ubuntu bug caused by an out-of-date kernel on the build farm. I'm working on an SRU to fix that. Please track further status on the Launchpad bug page given below. -- assi

[issue8326] Cannot import name SemLock on Ubuntu

Buck Golemon added the comment: @Barry: Yes, it's still a problem. The ubuntu 10.10 python2.7 still has no multiprocessing. Since the EOL is April 2012, it needs fixed. It may be considered an invalid python bug, since it seems to be strictly related to Ubuntu packaging, but I thought the pyt

[issue8326] Cannot import name SemLock on Ubuntu

Barry A. Warsaw added the comment: Is this still a problem for people? Ubuntu 11.04's python2.7 has been fixed: @neurotica[~:1000]% type python2.7 python2.7 is /usr/bin/python2.7 @neurotica[~:1001]% python2.7 -c 'from _multiprocessing import SemLock' @neurotica[~:1002]% The Launchpad bug for

[issue8326] Cannot import name SemLock on Ubuntu

Buck Golemon added the comment: python2.7.1+ from mercurial supports sem_open (and multiprocessing) just fine. doko: Could you help us figure out why the ubuntu 10.10 python2.7 build has this issue? I believe this issue should be assigned to you? Relevant lines from the config.log: configur

[issue8326] Cannot import name SemLock on Ubuntu

R. David Murray added the comment: Like Stefan says, use the default build options with the checkout. If it works, then the problem is an Ubuntu bug, and not a Python bug. -- ___ Python tracker __

[issue8326] Cannot import name SemLock on Ubuntu

Stefan Krah added the comment: Buck Golemon wrote: > > I suggest that you try to build from the above mercurial repository and see > > if the problem persists. > > How do I know the configuration options that the Ubuntu packager used? I'd use the default configuration and check if sem_open i

[issue8326] Cannot import name SemLock on Ubuntu

Sandro Tosi added the comment: > How do I know the configuration options that the Ubuntu packager used? the make file (likely) used is at: http://bazaar.launchpad.net/~doko/python/pkg2.7-debian/view/head:/rules Note: he is also a python developer, so you can add him to nosy and ask clarificat

[issue8326] Cannot import name SemLock on Ubuntu

Buck Golemon added the comment: > I suggest that you try to build from the above mercurial repository and see > if the problem persists. How do I know the configuration options that the Ubuntu packager used? -- ___ Python tracker

[issue8326] Cannot import name SemLock on Ubuntu

Stefan Krah added the comment: This line... >>> from multiprocessing.synchronize import Semaphore ... works on Ubuntu Lucid with the 2.7, 3.1, 3.2 and default branches from: http://hg.python.org/cpython Since you mention Ubuntu's build configuration, I suggest that you try to build from the

[issue8326] Cannot import name SemLock on Ubuntu

Changes by Buck Golemon : -- title: Cannot import name SemLock on Ubuntu lucid -> Cannot import name SemLock on Ubuntu ___ Python tracker ___

[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

[issue8326] Cannot import name SemLock

R. David Murray added the comment: Why do you think issue 3770 is not relevant? It looks from the traceback like the built version of multiprocessing decided that sem_open wasn't functional. So this sounds like a lucid packaging problem to me. -- components: +Extension Modules nosy:

[issue8326] Cannot import name SemLock

New submission from David Coconut : Operating system: Ubuntu 10.04 Lucid Lynx (Beta) This worked with Python 3.1 on 9.10 Karmic Koala. The same error appears on two separate installations of Lucid. Issue 3770 does not seem to be relevant here. Traceback (most recent call last): File "/usr/lib