Open carljm opened 3 months ago
One thing that we need to implement as part of this is a vendored filesystem. It's not a functionality but a task to complete on our way to get there.
One thing that we need to implement as part of this is a vendored filesystem. It's not a functionality but a task to complete on our way to get there.
Right. I was considering that part of
Use vendored typeshed stubs at runtime to resolve symbols to stdlib definitions if --custom-typeshed-dir is not passed
since, as you say, it's necessary to implement a vendored filesystem in order to be able to do that
(Or intentional choices to diverge from PEP 561 compliance.)
Subtasks:
--custom-typeshed-dir
internally: https://github.com/astral-sh/ruff/pull/11767--custom-typeshed-dir
is not passedVendoredFileSystem
implementation: https://github.com/astral-sh/ruff/pull/11863VendoredFileSystem
implementation to resolve stdlib stubs: #12224-stubs
installed intosite-packages
(must take priority over other packages installed intosite-packages
)VERSIONS
file: we shouldn't fallback to a typeshed module if theVERSIONS
file specifies it does not exist with the--target-version
the user passes.VERSIONS
: https://github.com/astral-sh/ruff/pull/11836VERSIONS
file when resolving stdlib modules: https://github.com/astral-sh/ruff/pull/12141._pth
files: