Directing PyCharm to Python 3.3 interpreter?

28,361

Solution 1

PyCharm detects Python 3.3 path automatically for the Python installed from http://python.org mpkg installer:

Path

/Library/Frameworks/Python.framework/Versions/3.3/bin/python3

Once you add this interpreter to PyCharm, install the package management tools (click on the Install 'distribute', then click on Install 'pip'):

pip

Upgrade pip to the latest version using the Upgrade button (distribute upgrade will fail).

Now you can install packages with the Install button, for example Django can be installed from the Interpreters dialog in PyCharm:

Django

If you have problems with code completion, try File | Invalidate Caches, restart PyCharm and wait until indexing is finished. For me it worked fine out of the box:

code completion works

Solution 2

Python 3.3 now uses a new virtualenv mechanism called venv.

You can create one of these environments using:

pyvenv myprojectname

PyCharm 3.0 does not handle these correctly. The old virtualenv system copied python binaries into the environment, while venv creates symbolic links to the python3.3 binary instead. PyCharm tries to resolve all these symbolic links, until it finds a real file. This results in it ignoring your virtual environment and using the global environment instead.

To work around this bug, you can copy the python3.3 binary into your environment's bin folder and then add this as the project's interpreter in PyCharm.

Share:
28,361
Adam
Author by

Adam

Updated on July 05, 2022

Comments

  • Adam
    Adam almost 2 years

    I'm not sure why I'm having so much trouble with this. I'm on OS X 10.7, and I installed Python with default settings and ran the .command file included.

    I just want to get PyCharm working with Python 3.3, but I can't seem to find a working interpreter. The only one I can find loads instantly (gives 'distribute' and 'setuptools' packages) and gives me 'some skeletons failed to generate' errors. If I choose one of the 2.7 interpreters it loads for a while but I still get a similar error. I also get some issue with Python packaging tools not being found (usually it's 'pip').

    I've searched for a long time but can't find a solution.

  • Adam
    Adam over 11 years
    Thanks, I wasn't able to get it working at the time, but I was already planning on reformatting that week and I got it working fine on a fresh OS install.