Tag Info

New answers tagged

0

The generic command 'python' and shebang '#!/usr/bin/python' currently map to Python 2. That will change to Python 3 in a future version of Ubuntu. Do NOT change that mapping yourself - it will break many essential system applications and services in 14.04 that still use Python 2, and won't work with Python 3 yet. Undo whatever you did to set Python 3.4 as ...


0

I found out what was wrong. #!/home/jesse/Desktop interpret Needed to be: #!/home/jesse/Desktop/interpret /usr/bin/env is a command itself. Python is an argument passed to it. Thanks to @muru for this.


0

The official build doc for python3 on ubuntu seem to be here.


0

Ok, I found the problem: both pip and pip3 install the executable file in /usr/local/bin. Uninstalling from pip (python2) removes the binary. So I had to uninstall and re-install in pip3 to get things working.


3

/usr/bin/python, /usr/bin/python2 and /usr/bin/python3 are just symbolic links to a Python executable for convenient access to a Python 2/3 interpreter or just a python interpreter. In 14.04 they point to: /usr/bin/python → /usr/bin/python2.7 /usr/bin/python2 → /usr/bin/python2.7 /usr/bin/python3 → /usr/bin/python3.4 In combination with virtualenv you ...



Top 50 recent answers are included