0

I want to avoid these kind of messages popping up, as I am not even using python 2.7. Note that the code runs fine.

I have tried the following things:

I am using a .sh wrapper around the python executable on the server as I want Pycharm to first source my ~/.bash_profile before using the interpreter (similar to this advice). I think that this might be the reason PyCharm doesn't recognize it as being python 3: if I point directly to the remote interpreter, the code compatibility issue dissappears.

Is there any way to keep the benefits of the wrapper and getting rid of these error messages?

Nathan
  • 1
  • 1

1 Answers1

0

You're right, PyCharm is unable to determine Python version and uses 2.7 as a fallback.

Since 2019.3 the latest Python is used by default (3.8 at the moment), please try the EAP build.

user2235698
  • 7,053
  • 1
  • 19
  • 27