when setting a PATHPATH, you cannot emerge python-r1 packages (causes sandbox violations). setting PYTHONPATH is a common way of installing python packages locally (for testing for instance) Reproducible: Always Steps to Reproduce: export PYTHONPATH="~/.python-apps" emerge -1 =dev-python/nose-1.1.2-r1 Actual Results: sandbox violation when portage tries to install to ~/.python-apps Expected Results: portage ignores the PYTHONPATH var I think that maybe we should have a generic environment variable that when set will allow portage to use the local environment variables. 'USE="asd" emerge foo' would become 'LOCAL_PORTAGE_ENV=true USE="asd" emerge foo'
these kind of env vars are not the purview of sandbox see bug 326887 for the general env topic. for this particular case, i think that'd be something the python eclasses would want to scrub.
Does this still happen? If so, I will take a look into fitting PYTHONPATH clearing into the eclass.
commit 2c7d60126fa1d4c4702201d62a1396ce7609de82 Author: Michał Górny <mgorny@gentoo.org> Date: Fri Dec 29 17:40:17 2023 +0100 profiles/info_vars: Add PYTHONPATH Signed-off-by: Michał Górny <mgorny@gentoo.org> (In reply to Michał Górny from comment #2) > Does this still happen? If so, I will take a look into fitting PYTHONPATH > clearing into the eclass. but yeah, it does
