setuptools installs two conflicting versions of pssh eggs
Closed this issue · 6 comments
GoogleCodeExporter commented
What steps will reproduce the problem?
1. install pssh 2.2.2 on Ubuntu 10.04.3
LTS 2.6.32-34-server #77-Ubuntu SMP Tue Sep 13 20:54:38 UTC 2011 x86_64
GNU/Linux
2. a ran ez_setup.py and setup.py
3. pssh gives
Traceback (most recent call last):
File "/usr/local/bin/pssh", line 24, in <module>
from psshlib.manager import Manager, FatalError
ImportError: cannot import name FatalError
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
pssh 2.2.2
Ubuntu 10.04.3
uname -a: LTS 2.6.32-34-server #77-Ubuntu SMP Tue Sep 13 20:54:38 UTC 2011
x86_64 GNU/Linux
python: Python 2.6.5 (r265:79063, Apr 16 2010, 13:57:41)
[GCC 4.4.3] on linux2
uname -m: x86_64
Please provide any additional information below.
Original issue reported on code.google.com by djminb...@gmail.com
on 23 Nov 2011 at 5:02
GoogleCodeExporter commented
Do you have another version of pssh installed on your computer by any chance?
Original comment by amcna...@gmail.com
on 23 Nov 2011 at 6:30
GoogleCodeExporter commented
Andrew - I am running into this issue too. I was running pssh 2.1.1
previously. What is the best way to uninstall pssh 2.1.1 if the issue is
having both installed?
Original comment by ryan.bro...@gmail.com
on 16 Jan 2012 at 9:13
GoogleCodeExporter commented
I was able to resolve the issue by deleting this file:
/usr/lib/python2.4/site-packages/pssh-2.1.1-py2.4.egg
Original comment by ryan.bro...@gmail.com
on 16 Jan 2012 at 9:36
GoogleCodeExporter commented
Hmm. It's disappointing that setuptools installs two files of different
versions side-by-side. I wonder whether there's a workaround.
Original comment by amcna...@gmail.com
on 19 Jan 2012 at 11:29
- Changed title: setuptools installs two conflicting versions of pssh eggs
GoogleCodeExporter commented
djminbild and ryan.brothers, am I correct in assuming that this is a setuptools
bug rather than a pssh bug? If so, I think this issue should be closed, but I
feel like you both have more insight about what's going on than I do.
I think I'll go ahead and close this issue for now, but please reopen it if you
think that there's anything we should do in pssh to address this. Thanks!
Original comment by amcna...@gmail.com
on 23 Jan 2012 at 7:23
- Changed state: Invalid
GoogleCodeExporter commented
Very helpful. On OSX, it was under
/Library/Python/[version-number]/site-packages/pssh-2.1.1-py2.7.egg
Original comment by rmarsc...@beaffinitive.com
on 4 Jun 2012 at 4:56