pylsp is confused by a script having the same name as a package it imports

[jy-lefort]

Consider the following file tree:

foo.py
foo/__init__.py

With contents:

# foo.py
from foo import *
bar()

# foo/__init__.py
def bar():
    print("bar")

This is legit Python and as expected, running python foo.py prints the string bar.

However, pylsp is confused by the fact that foo.py and the foo module have the same name, and won't visit the definition of bar() from foo.py. Renaming foo.py to foo2.py works around the issue.

[sterfield]

Just encountered the same issue, I was confused why pylsp was sending "no locations found" when I was trying to jump to symbol definitions.