The scripts that generate and read the /etc/profile.env file should also consider the PYTHONPATH variable to be SPECIAL. Reproducible: Always Steps to Reproduce: 1. Add a Python based package to /etc/env.d that uses PYTHONPATH. 2. 3.
i've never come across any python package that requires PYTHONPATH in env.d or profile.env. imo, that should be kept for the user to set, not for site-wide. this reminds me, maybe i should unset PYTHONPATH for all ebuilds that use distutils/python eclass.
Actually, it's my own package. It is a large collection of Python modules and rather than install them all in site-packages I just set the PYTHONPATH to point to it. I put something in /etc/env.d so that all the users on my system can access it. It is not in portage, however. BTW, the package is pyNMS: http://sourceforge.net/projects/pynms And yes, it would would nice to unset PYTHONPATH when doing ebuilds because my package also contains a sitecustomize module that automatically installs some extra builtins, and installs a debugger hook. I would rather that not run when running emerge. It does not seem to have a serious effect, but just in case.
I don't get it: what do you mean with "special" ?
genone: see env_update() in portage.py. Specials are incremental env variables. Specials change included in cvs.
supposed to be fixed in 2.0.50 which is stable now. If this bug is not fixed please reopen.
