Buck Golemon buck.gole...@amd.com 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,
Barry A. Warsaw ba...@python.org 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.
Matthias Klose d...@debian.org added the comment:
Barry A. Warsawba...@python.org 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
Barry A. Warsaw ba...@python.org added the comment:
On Apr 26, 2011, at 09:45 PM, Matthias Klose wrote:
Matthias Klose d...@debian.org added the comment:
Barry A. Warsawba...@python.org added the comment:
I'm closing this as invalid for Python, since I believe this is strictly an
Ubuntu
Barry A. Warsaw ba...@python.org 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
Buck Golemon buck.gole...@amd.com 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
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
Changes by Buck Golemon buck.gole...@amd.com:
--
title: Cannot import name SemLock on Ubuntu lucid - Cannot import name SemLock
on Ubuntu
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8326
Stefan Krah stefan-use...@bytereef.org 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
Buck Golemon buck.gole...@amd.com 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
Sandro Tosi sandro.t...@gmail.com 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
Stefan Krah stefan-use...@bytereef.org added the comment:
Buck Golemon rep...@bugs.python.org 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
R. David Murray rdmur...@bitdance.com 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 rep...@bugs.python.org
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
22 matches
Mail list logo
