> What is sysconfig.cfg?
A file containing the install schemes for packaging (not for distutils, these are still in distutils.commands.install) and the categories for data files, to allow installation to various directories for scripts, doc, etc (cf. FHS).  The idea AFAICT was to allow OS-level customization of the install paths with a config file instead of code patches.  There are already complaints about the sysconfig module API, so I wanted to avoid locking us into this new sysconfig.cfg file format without a longer discussion:
- is this file needed for built-from-source Pythons installed in e.g. /usr/local?
- should it apply to distributions installed using non-OS packaging tools with the OS Python?
- does it remove the need for the --layout=deb gross patch that you can see for example in Debian and derivatives? (i.e. a layout used to build Python projects in a debian/tmp/usr subdirectory of the source package, before using non-Python packaging tools to move these files to the right location)

These are the kind of questions from the top of my head which I think haven’t been hashed out.  Or maybe it’s perfectly clear between Tarek and the few OS packagers that discussed this matter but there is no documentation of that.  As the only client of the sysconfig.cfg file was packaging, I think the safe thing to do is to not add it in 3.3 and make it a part of the discussions for 3.4 (i.e. may need a PEP).