Hi Bill,
(Forgive the backslashes, when I type it comes natural as a windows
developer)
I think you found my problem(s), but I am not sure what to do to solve
them.
Typing in your commands from the LIVE and TEST directories containing
manage.py I found
> ---------------------------------
> import sys, os, pprint
> os.getcwd()
- LIVE returns: \home\project\src\projectfiles ;
- TEST returns: \home\test-project\src\projectfiles
> pprint.pprint(sys.path)
- LIVE & TEST both return the same as I'd expect. Not sure if /home/
test-project/src should be in there though, and if it should not be /
home/project/src:
['/home/projectt/src/projectfiles ',
'/home/test-project/src',
{lots of python 2.5 folders}
'..']
> import django
> django
LIVE & TEST return: <module 'django' from '/home/test-project/src/
django/__init__.pyc'>
****** I would have expected this to be '/home/project/src/django/
__init__.pyc' *****
In addition I also ran the following
-----------
import settings
settings.DATABASE_NAME = value in settings.py file that defines the DB
- LIVE returns: DBLIVE
- TEST returns DBTEST
So I am quite confused because
a) we deployed the Django source to both TEST and LIVE in order to
keep them separate for testing purposes
b) it looks like we are instead running the "wrong" copy of the django
source. So how do I change that? And once I change it, does it mean I
will not be able to run a separate loaddata.py for TEST?
c) is the correct setting returned above ovewritten by where the
django code being executed?
Sorry to hassle you further, but I'd really appreciate your help.
Regards,
Mauro
> ------------------------------------
On 19 Jan, 19:58, Bill Freeman <ke1g...@gmail.com> wrote:
> If you really are using backslash as a path separator on ubuntu, it
> could lead to
> various unexpected results.
>
> Also, if you're not doing so, cd into the directory containing
> manage.py before running
> the commands.
>
> Also, try the manage.py shell command, and at the prompt do:
>
> ---------------------------------
> import sys, os, pprint
> os.getcwd()
> pprint.pprint(sys.path)
> import django
> django
> ------------------------------------
>
> ...and see if you find any of the answers surprising.
>
> Beyond that, find the py file that implements the loaddata command, and
> choose a
> likely place to insert:
>
> import pdb;pdb.set_trace()
>
> And step along to see how it's finding its files.
>
> Good luck. Bill
>
> On Tue, Jan 19, 2010 at 1:38 PM, MauroCam <maurociac...@gmail.com> wrote:
> > Hi,
>
> > Please forgive the possibly daft question, but as an Ubuntu newbie I
> > am going crazy with the following problem.
>
> > I am seeing unexpected behaviour on our live production server,
> > running Ubuntu, when I execute manage.py
>
> > The site hosts two sites, the LIVE site and a mirror TEST site that we
> > use for final testing. The structure of the two sites is as follows
>
> > \home\project\src\projectfiles
>
> > \home\test-project\src\projectfiles
>
> > The \projectfiles directory contains settings.py
>
> > In both sites there is also a subdirectory
>
> > \projectfiles\maintenance\commands\loaddata.py
>
> > which contains a python file we use to load test data into the
> > database. This file used to execute by calling
>
> > ...\projectfiles\python manage.py loaddata
>
> > and worked for both LIVE and TEST.
>
> > Recently I had to upload significant changes to the LIVE so, I copied
> > the src folder, deleted the original and created a brand new src from
> > SVN. The structure is now
>
> > \home\project\src\projectfiles
> > \home\project\src\src_old\projectfiles
>
> > \home\test-project\src\projectfiles
>
> > When I now run
>
> > \home\project\src\projectfiles\python manage.py loaddata,
>
> > the file which actually executes the loaddata.py is the one in TEST
>
> > I have confirmed this by deleting
>
> > \test-project\maintenance\commands\loaddata.py.
>
> > and then re-executing the loaddata for the LIVE server. But this gave
> > an "Unknow command: loaddata" error.
>
> > Any advice on how to resolve this would be greatly appreciated.
>
> > P.S. I run through a test of the above on my PC running XP, and all
> > continues to work fine. So it looks like some Ubuntu/Linux issue.....
>
> > Thanks
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Django users" group.
> > To post to this group, send email to django-us...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > django-users+unsubscr...@googlegroups.com.
> > For more options, visit this group
> > athttp://groups.google.com/group/django-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@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.
