There is a bug in Python 2.6.1 (introduced in that version, it wasn't there in 2.6) which is that the CRT manifests aren't set up correctly. This prevents, for instance, compiling and using mod_python 2.6.1 against Apache without giving httpd.exe a manifest file.
http://bugs.python.org/issue4566 The good news is that this has been fixed in Python trunk; the bad news is that I don't know when Python 2.6.2 is scheduled. I would guess "after PyCon" http://www.python.org/community/pycon/ so some time in April maybe. On Mar 12, 8:43 pm, cjl <cjl...@gmail.com> wrote: > Sorry for the off-topic cross-post, but I have tried this question on > the other python lists to no avail, and there are some wicked smart > Python people that read this group. > > I am in the process of updating my little django project, > instantdjango.com, and I'm running into a little problem with my > 'build' script, which is a script I hacked together to create the > instant django portable environment, without me having to do > everything 'by hand'. > > With previous versions of the Python Windows msi installer, for > example 2.5.4, I could run the following command from the windows cmd > prompt (or from inside my build script): > > msiexec /a C:\python-2.5.4.msi /qn TARGETDIR=C:\python > > This would result in a 'full' python installation (or extraction) in > the C:\python directory, inside of which I would find the (necessary) > file msvcr71.dll. Of course, this would not register extensions, but I > did not want it to. > > When I try the same command with python-2.6.1.msi, the file > msvcr90.dll and the manifest file are not created in the python > directory, nor anywhere else on the system. > > If, instead, I double click the python-2.6.1.msi installer, the > msvcr90.dll file is created. I have tried msiexec with '/a' and '/i' > command line switches, and every possible combination of options, all > to no avail. > > I can't figure out if this is a regression, but it used to work. > > I am basing my attempts on the following > page:http://www.python.org/download/releases/2.5/msi/ > > I could not find a similar page for the 2.6 release. > > Can anyone point me in the right direction to figure out what I'm > doing wrong? > > I tried to understand the 'msi.py' file that is in the 'tools' > directory of the python source code, but it is pretty far over my > head. As near as I can figure, a setting is made in the gui which > tells the msi installer where to create the dll (shared or private), > and somehow this setting doesn't happen if the gui is not invoked. > > Thanks, > -cjlesh --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
