PyCharm shows unresolved references error for vali

Question

I am using PyCharm to work on a project. The project is opened and configured with an interpreter, and can run successfully. The remote interpreter paths are mapped properly. This seems to be the correct configuration, but PyCharm is highlighting my valid code with "unresolved reference" errors, even for built-in Python functions. Why don't these seem to be detected, even though the code runs? Is there any way to get PyCharm to recognize these correctly?

---

This specific instance of the problem is with a remote interpreter, but the problem appears on local interpreters as well.

Answer 1

Tested with PyCharm 4.0.6 (OSX 10.10.3) following this steps:

1. Click PyCharm menu.
2. Select Project Interpreter.
3. Select Gear icon.
4. Select More button.
5. Select Project Interpreter you are in.
6. Select Directory Tree button.
7. Select Reload list of paths.

Problem solved!

Answer 2

There are many solutions to this, some more convenient than others, and they don't always work.

Here's all you can try, going from 'quick' to 'annoying':

• Do File -> Invalidate Caches / Restart and restart PyCharm.
  • You could also do this after any of the below methods, just to be sure.
• First, check which interpreter you're running: Run -> Edit Configurations -> Configuration -> Python Interpreter.
• Refresh the paths of your interpreter:
  • File -> Settings
  • Project: [name] -> Project Interpreter -> 'Project Interpreter': Gear icon -> More...
  • Click the 'Show paths' button (bottom one)
  • Click the 'Refresh' button (bottom one)
• Remove the interpreter and add it again:
  • File -> Settings
  • Project: [name] -> Project Interpreter -> 'Project Interpreter': Gear icon -> More...
  • Click the 'Remove' button
  • Click the 'Add' button and re-add your interpeter
• Delete your project preferences
  • Delete your project's .idea folder
  • Close and re-open PyCharm
  • Open your project from scratch
• Delete your PyCharm user preferences (but back them up first).
  • ~/.PyCharm50 on Mac
  • %homepath%/.PyCharm50 on Windows
• Switch to another interpreter, then back again to the one you want.
• Create a new virtual environment, and switch to that environments' interpreter.
• Switch to another interpreter altogether, don't switch back.

Answer 3

I find myself removing and re-adding the remote interpreter to fix this problem when Invalidating Caches or Refreshing Paths does not work.

I use vagrant and every once and awhile if I add a new VM to my multi-vm setup, the forwarded port changes and this seems to confuse PyCharm when it tries to use the wrong port for SSH. Changing the port doesn't seem to help the broken references.

Answer 4

In my case the inspection error shows up due to a very specific case of python code. A min function that contains two numpy functions and two list accesses makes my code inspection give this kind of errors.

Removing the 'd=0' line in the following example gives an unresolved reference error as expected, but readding doesn't make the error go away for the code inspector. I can still execute the code without problems afterwards.

import numpy as np
def strange(S, T, U, V):
    d = 0
    print min(np.abs(S[d]), np.abs(T[d]), U[d], V[d])

Clearing caches and reloading list of paths doesn't work. Only altering the code with one of the following example patches does work:

• Another ordering of the 'min' parameters: schematically S U T V but not S T U V or T S U V
• Using a method instead of the function: S[d].abs() instead of np.abs(S[d])
• Using the built-in abs() function
• Adding a number to a parameter of choice: U[d] + 0.

Answer 5

If you want to ignore only some "unresolved reference" errors, you can also tell it PyCharm explicitly by placing this in front of your class/method/function:

# noinspection PyUnresolvedReferences

Answer 6

I closed all the other projects and run my required project in isolation in Pycharm. I created a separate virtualenv from pycharm and added all the required modules in it by using pip. I added this virtual environment in project's interpreter. This solved my problem.