Skip to content

make python user site-packages isolation in .local directory configurable #7707

@kalefranz

Description

@kalefranz

As described in #7671 (comment)

For activated non-base conda environments, conda activate will actually go ahead and set the PYTHONNOUSERSITE environment variable, I'm suggesting you do now yourself. By default it will not set it for the base environment, whether the base environment is properly activated or not. This behavior will all be configurable, and there appear to be three states to what we're proposing for python interpreter isolation from ~/.local: disabled, non-base, all. The default value for the configuration, as proposed, would be the non-base one.

xref: #448
xref: #7173

Metadata

Metadata

Assignees

No one assigned

    Labels

    locked[bot] locked due to inactivitysource::governancecreated by members of the conda governance (https://github.com/conda-incubator/governance)stale[bot] marked as stale due to inactivitystale::closed[bot] closed after being marked as staletype::featurerequest for a new feature or capability

    Type

    No type

    Projects

    Status

    🏁 Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions