-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Closed as not planned
Closed as not planned
Copy link
Labels
locked[bot] locked due to inactivity[bot] locked due to inactivitysource::governancecreated by members of the conda governance (https://github.com/conda-incubator/governance)created by members of the conda governance (https://github.com/conda-incubator/governance)stale[bot] marked as stale due to inactivity[bot] marked as stale due to inactivitystale::closed[bot] closed after being marked as stale[bot] closed after being marked as staletype::featurerequest for a new feature or capabilityrequest for a new feature or capability
Description
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.
Metadata
Metadata
Assignees
Labels
locked[bot] locked due to inactivity[bot] locked due to inactivitysource::governancecreated by members of the conda governance (https://github.com/conda-incubator/governance)created by members of the conda governance (https://github.com/conda-incubator/governance)stale[bot] marked as stale due to inactivity[bot] marked as stale due to inactivitystale::closed[bot] closed after being marked as stale[bot] closed after being marked as staletype::featurerequest for a new feature or capabilityrequest for a new feature or capability
Type
Projects
Status
🏁 Done