ok...
Try to do a ln -s (or simply move) of your django directory to the
/usr/local/lib/python2.4/site-packages directory, so you have:
/usr/local/lib/python2.4/site-packages/django/
Usually it's the place to put it. Maybe it's that...
G
On 12/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
1) django is at ~/lib/python2.4/django
2)Yes, but I was on dreamhost fcgi setup.
3 & 4) Pretty sure... I copied it over complete, and like I said, it
seems as though my models and templates are using it with no problems,
it's just manage.py that's cranky
--~--~-~--~~~
Where is your django installation at the moment?
Where you able to manage.py shell before the migration?
Are you sure you have all the __init__.py's necessary?
Are you sure it is not a permission issue?
G
On 12/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Yes, I have something very muc
Yes, I have something very much like that in my apache conf.
Yes, I have mod_python and apache2.
I can't run python manage.py * cause I get
ImportError: No module named django.core.management
I'm pretty sure no file was corrupted. It appears everything is finding
and using nesh.thumbnail with n
Comment out the statements that use the module throwing the ImportError,
open the shell in manage.py, check your path, try to import by hand, and
go from there. Do you have the proper __init__.py files for all modules?
Do you have the right directories in your path?
-jag
On Wed, 2006-11-29 at 20
Ok... blind try.
If your my_project is in /path/to/my_project, and you have your
manage.py in that directory, tr adding those lines:
import sys
sys.path.append('/path/to)
I have to manually add the parent directory to the sys.path in order
to use my applications.
G
On 12/1/06, [EMAIL PROTECTE
[EMAIL PROTECTED] a écrit :
> Please. Anyone... I just want to be able to use manage.py AND the
> project!
- are you sure that django is well installed on your server ?
- In your apache conf, do you have something like :
SetHandler mod_python
PythonHandler dja
Please. Anyone... I just want to be able to use manage.py AND the
project!
--~--~-~--~~~---~--~~
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
I can't run manage.py shell... can't run manage.py anything without it
throwing the importError.
I printed sys.path and didn't see anything odd, but I don't really know
what I'd be looking for. Here's what I get:
['', '/home2/baxter/lib/python2.4',
'/usr/local/lib/python2.4/site-packages/setuptoo
I'd start with "manage.py shell" and "import sys; print sys.path" to
look for anything unusual.
-jag
On Tue, 2006-11-28 at 21:19 +, [EMAIL PROTECTED] wrote:
> Yup... like I said, the models and templates and all appear to see it
> no problem. It's looks like it's just manage.py that's not se
Anyone? I'm wondering if it's a pythonpath issue, but don't really know
how to check (or fix).
I found one thread that suggested adding the project to sys.path within
manage.py, but that didn't help.
--~--~-~--~~~---~--~~
You received this message because you ar
Yup... like I said, the models and templates and all appear to see it
no problem. It's looks like it's just manage.py that's not seeing it.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To p
did you add it to your settings.py installed apps section?
--~--~-~--~~~---~--~~
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 fro
Another weird error since I changed servers and went from fcgi to
mod_python.
I have nesh.thumbnails installed alongside my main project, it's in
installed apps, and the models and templates see it fine. Manage.py, on
the other hand, doesn't. When I run
python2.4 manage.py validate (or manage.py
14 matches
Mail list logo