Reputation: 2672
I can move to a python project directory (say c:\www\myproject) and then issue
python manage.py shell
and then I can use all modules from django project, say the following piece of commands from the shell command:
import settings
from django.template import Template, Context
t=Template("My name is {myname}.")
c=Context({"myname":"John"})
f = open('write_test.txt', 'w')
f.write(t.render(c))
f.close
now, when I tried to collect all my commands into a python script, say "mytest.py", I cannot execute the script. I must missed something important.
I issued python mytest.py
then I got Import error: could not import settings
Is it on sys path?"
I'm in the project directory where settings.py resides.....
Could some one help me out?
thanks.
Upvotes: 30
Views: 58003
Reputation: 104
Here is yet another variant: I wrote and often use a management command "run" which has the advantage that scripts can see their command-line parameters:
http://lino-framework.org/api/lino.management.commands.run.html
Upvotes: 0
Reputation: 649
Saw in https://stackoverflow.com/a/24456404/4200284 a good solution for Django >= 1.7 and in case someone uses django-configurations this worked for me:
import sys, os, django
sys.path.append('/path/to/project')
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "config.local") # path to config
## if using django-configurations
os.environ.setdefault("DJANGO_CONFIGURATION", "Local")
from configurations import importer
importer.install()
django.setup() ## apparently important for django 1.7
from foo.models import Bar
print Bar.objects.all()
Upvotes: 1
Reputation: 101
Instead of manually adding things to your python script, or having to fit in the management command format, in case this is not something that needs to stay around long, you can get all the benefits of the Django environment by running your script with ./manage.py runscript <myscript.py>
... but if your script is in your project folder, then you can just add this line to the top of the python script: import os; os.environ['DJANGO_SETTINGS_MODULE'] = 'settings'
Upvotes: 2
Reputation: 8778
This method is deprecated in Django 1.4. Use django.conf.settings.configure()
instead
(see @adiew's answer for example code).
Old method follows.
Put this at the beginning of your script
from django.core.management import setup_environ
import settings
setup_environ(settings)
This is really what the manage.py does behind the scene. To see it view the Django source in django/core/management/__init__.py
. After executing these lines everything should be just like in ./manage.py shell
.
Upvotes: 23
Reputation: 714
Try put these two lines at the beginning of your script:
from django.conf import settings
settings.configure() # check django source for more detail
# now you can import other django modules
from django.template import Template, Context
Upvotes: 11
Reputation: 20008
To import Django's settings use:
from django.conf import settings
Upvotes: 2
Reputation: 20008
Try using a Django management command instead.
# myproject/myapp/management/commands/my_command.py
from django.core.management.base import NoArgsCommand
from django.template import Template, Context
from django.conf import settings
class Command(NoArgsCommand):
def handle_noargs(self, **options):
t=Template("My name is {myname}.")
c=Context({"myname":"John"})
f = open('write_test.txt', 'w')
f.write(t.render(c))
f.close
And then (if you follow the docs) you will be able to execute the command in the following fashion:
python manage.py my_command
Upvotes: 23