On Mon, 2006-06-05 at 17:57 -0700, keukaman wrote: > Thanks Adrian. I tried this approach and got a bunch of python errors > when trying to access my website. I manually deleted the contents of > the original django directory. Then I put the trunk django directory in > it's place. is there a step I may be missing? Do I need to run an > install package?
Could you be more specific than "a bunch of errors"? Are they errors because you haven't upgraded your porject to take account of the changes for magic removal. Or because you have some old *.pyc in place that cannot be overwritten by the webserver because it doesn't have write permissions in that directory? Or ... (the possibitilies are large). :-) Let us know a summary of what you are seeing (I mean, don't cut and past 27 pages of errors, but some details would be good) and we should be able to help. As far as what *must* be done to install Django from another directory, there is not really much. The django/ subdirectory should be available on your Python path and that is all. No install script or compilation required, since it's all just a very standard Python package. If you can start up a python prompt with the same PYTHONPATH setting as your webserver will be using and run "import django", then you are 90% of the way there. Anyway, post a few more details about the problems you are seeing and we'll see what shakes out. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
