Why do I get an 'SDK seems invalid' error when setting up my Project Interpreter in PyCharm?

Question

enter image description here

I try to set up project interpteter Python 3.5 in Pycharm and get an SDK error?

Any solution to fix it?

Did you just copy python34.exe to your desktop? Python is normally not installed into the desktop directory. — yole, Jan 06 '16 at 17:27

score 29 · Answer 1 · answered Aug 10 '18 at 09:36

29

did you move the whole project after you open it with pycharm? if so, just remove the .idea/* (run rm -r .idea under you project)

This problem is caused by: pycharm will create a .idea file under the project after the first time you import the project. SO the path in there will remain the old one after you moved the project. Thus the pycharm will keep trying to import 'old_path/venv/bin/activate' which is kept in .idea/*

answered Aug 10 '18 at 09:36

Yicheng Feng

299
3
2

I reinstalled Python, recreated vritualenvs and this was the key to my problems seemingly. At least to some of them. – Csaba Toth Jan 22 '19 at 22:37
This solution works like a charm! – Neverfaraway Aug 01 '23 at 22:44

score 5 · Answer 2 · answered May 03 '18 at 09:55

5

I had such problem. The solution was pretty easy. I created an account in russian in Windows, and you could emphasize that the error message (the big one) then contains the word about encoding is used. Therefore check your Windows account name - change it if it's not in english and contains spaces and other unwanted signs. Thanks.

answered May 03 '18 at 09:55

Sergei Shumilin

411
5
17

As of PyCharm 2022.2.2, PyCharm will still give you this error if you have a space in your Windows username or path to Python executable. I worked around this by making a symlink to the Python directory, without using spaces. – Albert S Nov 03 '22 at 18:43

Nathan Wailes · Answer 3 · 2018-11-09T17:24:09.650

I just had this error and got around it, and long-story-short I think it may have had to do with my PATH / PY_HOME / PYTHONPATH environment variables pointing to a different version of Python. Here's what I did:

Background:

In my case, I was trying to get a Python 2.7 venv running on a laptop where I'd previously been working with Python 3.
I'm using Windows 7.

Solution:

Hit the Windows key to pop up the Start menu.
Type out 'path' and hit Enter.
The 'Environment Variables' window should appear.
- There should be two sections of the window:
  1. One should say, "User variables for your_user_name".
  2. The other should say "System variables".
In both sections of the window, look for and edit (if they exist) the PATH, PYTHONPATH, and PY_HOME environment variables.
1. I removed any references to Python 3.
2. I set the PY_HOME variable to C:\Python27 (or whatever the path is to the Python installation you're trying to get working in PyCharm.)
I also deleted my installation of Python27 and reinstalled it, but I'm not sure that that was necessary.
Restart PyCharm.

score 2 · Answer 4 · answered Oct 17 '17 at 03:44

2

I got the same problem on windows 10, and got the solution.

PyCharm_Python_error.png

Root cause: - Python cannot be launched due to no python27.dll.

Solution: - Install python or put python27.dll in PATH

Thanks.

answered Oct 17 '17 at 03:44

Lon

21
3

score 2 · Answer 5 · answered Apr 16 '21 at 14:15

2

In my case, python.exe that I had in my venv was the problem.

Thus, I downloaded a specific version of Python and pasted contests of its Script folder to my \venv\Scripts folder.

answered Apr 16 '21 at 14:15

Başar Söker

606
8
16

score 0 · Answer 6 · answered Feb 14 '18 at 20:34

A fix for this issue, is tell to the global var named-> LD_LIBRARY_PATH to include the new python libraries compiled. Let's assume that you have just download python, extracted it & installed; assume that you have downloaded the 3.6.4 version

For include the library, you have to edit your .bashrc file. (This file is quite interesting, have a look ;) ). This file is an "hidden file" placed in your home: nano ~/.bashrc is a quite easy text editor. Go at the end of the file and append this command, replacing your path of new python export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/whoami/Downloads/Python-3.6.4

CTRL+X for save file.

For load the new file:

source ~/.bashrc

score 0 · Answer 7 · answered Jun 26 '18 at 18:01

Operating system: Windows 10 / cygwin

Desired Python: 2.7.14

Error: "SDK seems invalid"

My fix:

Remove Python 64 bit version
1. Install Python 32 bit version
2. using the windows environment variable dialog set PY_HOME={somedrive}\{somepath}\Python27
  PYTHONPATH={somedrive}\{somepath}\Python27

note: I guess it works since the errors I see are python generated eg "Traceback (most recent call last): File ..."

score 0 · Answer 8 · answered Dec 19 '18 at 07:10

I just ran into the same problem with Python 3.6 (which I wanted to use) and Python 3.7 also installed in my computer. My solution was just to remove reference to Python 3.7 from System PATH.

So my PATH is currently set:

C:\Program Files\Python36\Scripts\
C:\Program Files\Python36\

That's all, hope it helps.

score 0 · Answer 9 · answered Sep 23 '20 at 17:22

I had the same issue. I suspect it occurred whilst i was doing a python project, I was trying to make tensorflow run on my GPU, messing with settings I didn't and still dont really understand (in the terminal with path variables)

The issue in my case was with my system interpreter. I fixed it by going to the interpreter section in Pycharm and creating a choosing a new interpreter. I edited the "Path" environment\system variables from "...\python.exe\Scripts" to "...\python.exe"

score 0 · Answer 10 · answered Oct 07 '21 at 13:51

In my case (on a Windows os), the problem was due to the fact that I added a PYTHONHOME environment variable in an unrelated test of Apache2.4 + Flask: That "broke" the set up virtual environments using Conda. I started to get the "invalid SDK" error described above when I created a virtual environment which needed a version of Python different from the one indicated in PYTHONHOME (in my case, I needed a virtual environment running Python 3.6, while PYTHONHOME pointed to 3.8 version).

Solution: I simply needed to remove the PYTHONHOME environment variable!

henrry · Answer 11 · 2022-08-04T17:02:50.117

0

This work for me:

My environment created with python 3.9.1 but I install python 3.8 when I uninstall python 3.8 then restart and install python 3.9.1 version that set up in Pycharm correctly.

Note: After uninstall its important restart OS then after restart install python version compatible with environment created .

edited Aug 04 '22 at 17:02

answered Aug 04 '22 at 13:58

henrry

486
6
25

score 0 · Answer 12 · answered Mar 19 '23 at 22:32

0

For me, the problem was that part of the path of the project was in Hebrew, so when I changed it to English the problem was solved :)

answered Mar 19 '23 at 22:32

Ohad Sharet

1,097
9
15

Ciro Santilli OurBigBook.com · Answer 13 · 2019-09-26T09:23:36.420

PyCharm picks up random files of format ~/.asdfqwer/python as the Python executable or environment

On Ubuntu 19.04 pycharm-community 2019.2.3 installed with the snap, PyCharm for some weird reason picks up anything with the form:

~/.asdfqwer/python

up as a virtualenv Python interpreter and uses that as the default.

In my particular case, I had a file called:

~/.gdbinit.d/python

for my GDB Dashboard, which is not at all a python interpreter or virtualenv, just a python GDB config as opposed to a .gdb config.

To solve it, I just had to set the correct interpreter at:

File
Settings
Project: <project-name>
Project Interpreter
Dropdown with the random python interpreter selected
Show all
Delete the random interpreter wit -
Add the correct interpreter with +

Why do I get an 'SDK seems invalid' error when setting up my Project Interpreter in PyCharm?

13 Answers13

Linked