What happened?
When using the standard venv, Ty in vscode is not able to find to use the venv due to the pyvenv.cfg using relative paths as far as I could understand.
py_venv(
name = "venv",
tags = ["manual"],
deps = all_requirements,
)
This might be a Ty issue not sure.
Version
Development (host) and target OS/architectures:
Windows
Output of bazel --version:
8.5.1
Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file:
Language(s) and/or frameworks involved:
How to reproduce
py_venv(
name = "venv",
tags = ["manual"],
deps = all_requirements,
)
bazel run //:venv
If you select .venv/bin/python3 in vscode as interpreter it makes Ty crash.
Any other information?
No response
What happened?
When using the standard venv, Ty in vscode is not able to find to use the venv due to the pyvenv.cfg using relative paths as far as I could understand.
This might be a Ty issue not sure.
Version
Development (host) and target OS/architectures:
Windows
Output of
bazel --version:8.5.1
Version of the Aspect rules, or other relevant rules from your
WORKSPACEorMODULE.bazelfile:Language(s) and/or frameworks involved:
How to reproduce
py_venv( name = "venv", tags = ["manual"], deps = all_requirements, ) bazel run //:venv If you select .venv/bin/python3 in vscode as interpreter it makes Ty crash.Any other information?
No response