Importing bazel-generated code in the same directory as source files

[djacobowitz-aur]

We have a monorepo built by bazel, and it's common to have Python source files and proto files in the same directory. After a build this will end up with a runfiles directory that has the generated code and symlinks to the source files, which works fine. During development it's more trouble: the source files are in the source directory and the generated files are in bazel-bin. Like this:

bazel-bin/module/builddir.py
module/srcdir.py
main.py

pyright can resolve from module import srcdir and from module import builddir, but it can't resolve from module import (srcdir, builddir). It seems to map module to one directory or the other. Complete example attached. Is there a way to configure pyright to make this work? It's hard to call pyright's behavior wrong here, but it's certainly inconvenient for me.
pyworkspace.tar.gz

Here's the pyright output:

% ~/.local/bin/pyright --verbose
Loading configuration file at /home/djacobowitz/src/pyworkspace/pyrightconfig.json
No include entries specified; assuming /home/djacobowitz/src/pyworkspace
Auto-excluding **/node_modules
Auto-excluding **/__pycache__
Auto-excluding **/.*
Assuming Python version 3.10.12.final.0
Execution environment: python
  Extra paths:
    /home/djacobowitz/src/pyworkspace/bazel-bin
  Python version: 3.10.12.final.0
  Python platform: Linux
  Search paths:
    /home/djacobowitz/.local/lib/python3.10/site-packages/pyright/dist/dist/typeshed-fallback/stdlib
    /home/djacobowitz/src/pyworkspace
    /home/djacobowitz/src/pyworkspace/bazel-bin
    /home/djacobowitz/src/pyworkspace/typings
    /home/djacobowitz/.local/lib/python3.10/site-packages/pyright/dist/dist/typeshed-fallback/stubs/...
    /usr/lib/python3.10
    /usr/lib/python3.10/lib-dynload
    /home/djacobowitz/.local/lib/python3.10/site-packages
    /home/djacobowitz/.local/lib/python3.10/site-packages/rerun_sdk
    /usr/local/lib/python3.10/dist-packages
    /usr/lib/python3/dist-packages
Found 4 source files
Could not import 'annotationlib' in file '/home/djacobowitz/.local/lib/python3.10/site-packages/pyright/dist/dist/typeshed-fallback/stdlib/typing.pyi'
Could not import 'annotationlib' in file '/home/djacobowitz/.local/lib/python3.10/site-packages/pyright/dist/dist/typeshed-fallback/stdlib/typing.pyi'
Could not import 'annotationlib' in file '/home/djacobowitz/.local/lib/python3.10/site-packages/pyright/dist/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi'
Could not import 'annotationlib' in file '/home/djacobowitz/.local/lib/python3.10/site-packages/pyright/dist/dist/typeshed-fallback/stdlib/typing_extensions.pyi'
pyright 1.1.405
/home/djacobowitz/src/pyworkspace/main.py
  /home/djacobowitz/src/pyworkspace/main.py:3:29 - error: "builddir" is unknown import symbol (reportAttributeAccessIssue)
1 error, 0 warnings, 0 informations
Completed in 0.477sec

[erictraut]

No, this isn't supported. See this issue for details.

Supporting this would be theoretically possible, but it would require a pretty heavy lift because it breaks an assumption that's baked deeply into pyright's current design. Fixing it would also probably have a negative performance impact for most pyright users, so it's something I'd consider implementing only if there was significant signal from users. You're not the first person who has requested this support, but there have been only a handful of requests in the last five years — not enough to justify such a major change.

[djacobowitz-aur]

Thanks.