Closed
Description
How to reproduce:
ondrej@hawk:/tmp$ virtualenv-2.7 xx
New python executable in xx/bin/python
cInstalling setuptools............done.
Installing pip...............done.
ondrej@hawk:/tmp$ source xx/bin/activate
(xx)ondrej@hawk:/tmp$ pip install sympy
Downloading/unpacking sympy
Downloading sympy-0.7.2.rc1.python3.tar.gz (5.3Mb): 5.3Mb downloaded
Running setup.py egg_info for package sympy
Traceback (most recent call last):
File "<string>", line 14, in <module>
File "/tmp/xx/build/sympy/setup.py", line 36, in <module>
import sympy
File "sympy/__init__.py", line 27, in <module>
raise ImportError("It appears 2to3 has been run on the codebase. Use "
ImportError: It appears 2to3 has been run on the codebase. Use
Python 3 or get the original source code.
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "<string>", line 14, in <module>
File "/tmp/xx/build/sympy/setup.py", line 36, in <module>
import sympy
File "sympy/__init__.py", line 27, in <module>
raise ImportError("It appears 2to3 has been run on the codebase. Use "
ImportError: It appears 2to3 has been run on the codebase. Use Python
3 or get the original source code.
----------------------------------------
Command python setup.py egg_info failed with error code 1 in /tmp/xx/build/sympy
Storing complete log in /home/ondrej/.pip/pip.log
So first of all, it should not install the rc1 version, but the latest release. Second of all, it should not install the Python 3.x version when using Python 2.7.
More analysis by Aaron here:
https://groups.google.com/d/msg/sympy/JEwi4ohGB90/x0UEm2WIwlQJ