On Tue, Feb 19, 2008 at 4:28 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> On Feb 19, 2008 4:06 PM, RichardH <[EMAIL PROTECTED]> wrote: > > > > > Karen, > > Thanks for your analysis. Yes, I can confirm that I don't have the > > locale files either. > > Deleting my Django install and "running python setup.py install" does > > a correct install on mine as well. > > I would be interested to hear if anyone knows why the difference > > between python setup.py and setup.py? > > > I've dug into this a little further and the different results seem to be > caused by different values of the __file__ variable depending on how the > script is invoked. On Windows using 'setup.py install', __file__ is > fully-qualified (e.g. 'C:\path\to\django\setup.py') whereas with 'python > setup.py install', __file__ is simply 'setup.py'. The fuly-qualified > version causes problems since it finds its way into the destination > directory for the data files, so data files don't get copied to the > installation target directory. > > Still looking into what the right fix is, but at least now it seems like > we've got a handle on what the problem is. It's been popping up on the list > for quite a while, and I've always found it mysterious since I could never > recreate it. > > Malcolm checked in a fix for this problem yesterday (changeset 7139). So as of that revision, setup.py on Windows should work regardless of whether the command starts with "python". Hopefully that's the last of the mysterious missing admin templates. Cheers, Karen --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
