On 17 May, 2011, at 17:36, Tarek Ziadé wrote: > Hello > > I am about to merge packaging in the stdlib, and we will continue our > work there :) > > The impact is: > > - addition of Lib/packaging > - addition of test/test_packaging.py > - changes in Lib/sysconfig.py > - addition of Lib/sysconfig.cfg > > For the last one, I would like to make sure again that everyone is ok > with having a .cfg file added in the Lib/ directory. If not, we need > to discuss how to do this differently. > > == purpose of sysconfig.cfg == > > The sysconfig.cfg file is a ini-like file that sysconfig.py reads to > get the installation paths. We currently have these paths harcoded in > the python module. > > The next change I have planned is to allow several levels of > configuration, like distutils.cfg does. sysconfig.py will look for a > sysconfig.cfg file in these places: > > 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. > 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? Ronald
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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
