On Tue, May 17, 2011 at 7:21 PM, Ronald Oussoren <ronaldousso...@mac.com> wrote: ... >> 1. the current working directory -- so can be potentially included in >> a project source release > > Does this mean that python behaves differently when there happens to be a > sysconfig.cfg file in the current working directory? That's a potentional > security risk.
The use case is to have it there at install time so packaging can have alternative locations if needed. We could also drop the working dir scanning and have it: 1- passed explicitly to the pysetup script via an option. 2- used only if found in a root of a project at installation time, and only then > >> 2. the user home (specific location be defined, maybe in ~/local) >> [inherits from the previous one] > > How hard would it be to disable this behavior for tools like virtualenv and > py2app? Not hard at all, just an option. And the goal is also to allow virtualenv to have its own copy, like it does for distutils.cfg > > Ronald -- Tarek Ziadé | http://ziade.org _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
