Please, elaborate. I’m under the impression it already does when starting, based on my experiences using Python on Debian, Windows, and MacOS, all of which have different search paths that must be addressed early on.
Not totally. There’s a handful of ways to get to the interpreter that do much more work than what the standard executable does, such as the embedding of CPython in an application like Wireshark. However, these are approximately out of scope for PEP 582, from what I can tell.
Please elaborate: This adds a firmly opt-in pattern to searching for packages. Assuming that “it must be either next to the module that main confers or next to a pyproject.toml or version control boundary” requires a very specific hoop to be gone through in order to make this behavior useful.
Meanwhile, tools like git
get shelled straight into people’s shell. The startup latency for a few recursive checks is meaningless.
Google (TensorFlow) and Amazon (SageMaker) both basically ignore Conda’s existence, mostly because of its tight connections to Conda, Inc.
This was specifically why I suggested "recurse up until you find a pyproject.toml
or .(git|svn|etc)
next to a __pypackages__
, or reach the homedir/root.
There are cases where you’d have mixed users (e.g. symlinks in a handful of places, devcontainers, etc.)