On Sat, Jun 21, 2008 at 9:22 AM, sggottlieb <[EMAIL PROTECTED]> wrote:
> Thanks Karen! That was the issue. > Glad that was it, and it sounds like you could fix the symptom. To get a real fix implemented it would be helpful for you to post details of your system (new install, upgrade from an earlier OS X, whether a Macports version of Python had been installed, how you installed Django and what version) to that ticket (http://code.djangoproject.com/ticket/7414). I don't think we have a good handle yet on what set of circumstances, exactly, causes this to happen. Just several reports on this group of people hitting it and manually fixing it by copying over directories themselves. It would be nice if we could do something to fix the root problem, but first someone has to understand when and why it is happening. (A similar problem on Windows turned out to result from one and only one variant of 'python setup.py install' and 'setup.py install' neglecting to copy the installation data files, so it could be something very subtle that triggers the problem.) Thanks, 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 -~----------~----~----~----~------~----~------~--~---
