Closed GoogleCodeExporter closed 9 years ago
Hi Stephan,
(gc3pie@googlecode.com, Mon, Oct 07, 2013 at 10:05:53PM +0000:)
| What is the expected output? What do you see instead?
| I expect (hope) for a smooth install. However, the command results
| in a termination with the output included, below.
| [...]
| Downloading/unpacking boto (from gc3pie)
| Downloading boto-2.10.0.tar.gz (1.0Mb): 1.0Mb downloaded
| Running setup.py egg_info for package boto
| Traceback (most recent call last):
| File "<string>", line 14, in ?
| File "/home/hpc2700/gc3pie/build/boto/setup.py", line 45
| with open("README.rst") as f:
| ^
| SyntaxError: invalid syntax
the issue here is with the Python version: CentOS/RHEL 5.x ships
Python 2.4, which is not supported anymore by many packages that
GC3Pie depends upon. Here the error comes from the Boto library (used
for interacting with EC2-type clouds), which requires Python 2.6+.
Would it be possible to install Python 2.6 (or 2.7, even better) on
your cluster? You can find a survey of ways to install Python 2.6 on
a CentOS 5 at:
http://stackoverflow.com/questions/1465036/install-python-2-6-in-centos
I suggest using the EPEL repository (first answer), although that
requires some cooperation from the cluster sysadmins.
Original comment by riccardo.murri@gmail.com
on 8 Oct 2013 at 2:09
I gather that this is solved now and you have a working installation of GC3Pie?
Original comment by riccardo.murri@gmail.com
on 18 Oct 2013 at 6:08
Yes, solved with python 2.7
Original comment by stephan....@carleton.ca
on 18 Oct 2013 at 11:42
May I ask you if you had to ask the sysadmins to install Python, or did you
manage to install ActiveState Python in your home directory, or ...?
Original comment by riccardo.murri@gmail.com
on 18 Oct 2013 at 12:48
a number of newer python version have been available and the sysadmins pointed
me to them
Original comment by stephan....@carleton.ca
on 18 Oct 2013 at 1:12
This issue was closed by revision r3771.
Original comment by antonio....@gmail.com
on 28 Nov 2013 at 2:19
Original issue reported on code.google.com by
stephan....@carleton.ca
on 7 Oct 2013 at 10:05