pyright incorrectly adds the script directory to the module search path

[DetachHead]

# foo/a.py
a = 1

# foo/b.py
import a # no pyright error

# main.py
import foo.b

running python main.py will cause the following error:

> python main.py
Traceback (most recent call last):
  File "C:\project\main.py", line 4, in <module>
    import foo.b
  File "C:\project\foo\b.py", line 4, in <module>
    import a  # no error
    ^^^^^^^^
ModuleNotFoundError: No module named 'a'

[erictraut]

Pyright is working as designed here. This isn't a bug.

Refer to this documentation for details.

[DetachHead]

@erictraut that's not related to this issue. the problem is that when running a python file as a module, the imports are not relative to the location of the file.

# foo/a.py
a = 1

# foo/b.py
import a # no pyright error
# should be `import foo.a`

> python -m foo.b
ModuleNotFoundError: No module named 'a'

[erictraut]

See this documentation (item 6) that describes why this behavior is intended.

[DetachHead]

there should be an option to disable that behavior imo, since many projects do not intend for all of their python files to be executed as scripts like that