Tarek Ziadé wrote: > Now for the format problem, I agree that it seems more robust to > pre-process the variables > and inject them in the stdlib when ./configure is run. > > I am not sure what is the best strategy here, but I would rather not > add yet another > configuration file (wether its an xml format or an ini-like format). > > 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"
Are you planing to implement the proposal for Windows, too? There may be no need to change the code because we have full control over the official installers. Also the VisualStudio Windows build doesn't use ./configure but hand crafted header files. You'd have to fall back to a hand crafter sysconfig.py. Christian _______________________________________________ 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
