On Thu, Nov 19, 2009 at 11:04 AM, Antoine Pitrou <solip...@pitrou.net> wrote: > Tarek Ziadé <ziade.tarek <at> gmail.com> writes: >> >> So what I am proposing is to inject those values in a private dict in >> the new sysconfig.py module, >> that can be read through the get_config_vars / get_config_var APIs. >> >> This means that sysconfig.py will be added as "sysconfig.py.in" > > This means you have to relaunch the whole configure thing each time you make a > change to sysconfig? This doesn't sound like a good idea to me. You could make > the private dict a dedicated module instead, e.g. "_sysconfig_data.py.in".
That's much better indeed. > > As for Windows, if people have the ability to choose the installation > directory > when installing, I'm not sure how you're gonna handle it. I don't know. I am investigating with what Christian has explained on Windows installers, to see how it can be hooked in the installation process, and a fallback for the win32 build version. If it gets too complex, I'll probably postpone this and finish a first version of sysconfig that does use Makefile. Tarek _______________________________________________ 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
