> > (Hmm, is changing Modules/Setup enough to sort the Windows build out > > as > > well? Or does that need a separate change to some of the Visual > > Studio files?) > > The latter. Whenever you add, remove, or rename an extension module, > you need to adjust the PCbuild files as well. (technically, you also > have to adjust PC/os2emx/Makefile, PC/os2vacpp/makefile.omk, and PC/VC6, > but these changes are waived).
Correct me if I'm wrong, but in this case we are talking about adding a new directory to sys.path, correct? On Windows, this means a change in PCBuild/pyconfig.h and tools/msi/msi.py. A patch seems simple, so I'll check one in (assuming noone beats me) after clarification of a couple of points. * I assume lib-old should go at the end of the sys.path managed by the above files? * What is the story with "plat-win"? pyconfig.h includes a 'Lib\plat-win' directory, and although this directory does not exist, it usually ends up on sys.path. msi.py does *not* include this entry, which means it doesn't end up on sys.path in certain embedding environments (specifically, when the hosting application is using a python.dll located outside the Python directory). I'm sure there are pros and cons for including that directory, but I can't see justification for it to sometimes be used and sometimes not. So should I change msi.py to include this directory, or change pyconfig.h to not include it? Thanks, Mark _______________________________________________ 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
