A couple of the potential issues I can think of for Conda users include:
- The presence of a
__pypackages__dir meaning that installers will install into it by default, rather than the active environment, which has the same issues as the parallel pip and conda prefixes proposed and discussed above, along with it meaning whetherpipinstalls into a Conda env or__pypackages__depends on the user’s CWD, and impossible for Conda to manage - Python adds it to
sys.pathand any packages here will shadow any pip or conda installed packages in the Conda env, potentially breaking the environment and with no opportunity for Conda to detect or warn about it (as it can withpip-installed packages in its ownsite-packages)
As far as I’m aware, that was just informed speculation by Conda-using community members that it would likely not be practical or desirable for Conda as an installer to implement this PEP, not that the PEP would have no effect on the UX of Conda users as a whole.