On Mon, 7 Mar 2022, 7:42 pm Victor Stinner, wrote:
> On Fri, Mar 4, 2022 at 1:37 PM Eryk Sun wrote:
> > I don't understand. The site packages directories, including virtual
> > environments, are a site extension.
>
> I propose to change that. Move all code related to sys.path from the
> site
On Fri, Mar 4, 2022 at 1:37 PM Eryk Sun wrote:
> I don't understand. The site packages directories, including virtual
> environments, are a site extension.
I propose to change that. Move all code related to sys.path from the
site module to the Modules/getpath.py module.
Victor
--
Night
Hi,
I will add a link to
https://docs.python.org/dev/c-api/init_config.html#python-path-configuration
as we're trying to at least mention every way sys.path can be initialised.
I think the audience for the C API docs are likely to be more knowledgeable
than those reading the Setup and Usage
On 3/4/22, Victor Stinner wrote:
> it would be nice to move the last bits of the sys.path initialization
> from the site module to the getpath module. It's unpleasant to
> have a different sys.path depending if the site module is loaded
> or not.
I don't understand. The site packages
Unrelated to the doc, now that getpath has been rewritten in pure
Python, thanks to Steve Dower!, it would be nice to move the last bits
of the sys.path initialization from the site module to the getpath
module. It's unpleasant to have a different sys.path depending if the
site module is loaded or
Hi,
I tried to document inputs and outputs of Modules/getpath.py in the C
API Initialization API:
https://docs.python.org/dev/c-api/init_config.html#python-path-configuration
I don't know if it would be possible to merge most of these
information at a single place to avoid oudated documentation.
