python -c "
import sys
sys.path = sys.path[1:]
import django
print(django.__path__[0] +'contrib/admin/templates/admin/base_site.html')"
2015-06-07 1:18 GMT-06:00 shimanyi valentino :
> python -c "import syssys.path = sys.path[1:]import
> djangoprint(django.__path__)"
>
>
--
"La utopía sirve
Thanks for your swift responses Gergely. It's much appreciated ;-)
I will try again for the django-admin command
Oscar
Le dimanche 7 juin 2015 14:26:39 UTC+2, Oscar Buijten a écrit :
>
> Hi There,
>
> For various reasons I recently started efforts to covert an existing .php
> application to pyhto
Hello,
Sorry, I forgot that relative imports don’t work in standalone scripts,
just modules. In this case, yes, you should go on with the original import
line of yours, and modify the loading path. However, if you want to use
your models outside of Django, that is 1) pretty much unsupported and 2)
Thanks Gergely! :-)
I followed your suggestions and it does seem to improve behaviour, however,
I now get a new error...
-- snip --
Traceback (most recent call last):
File "historic_data_collector.py", line 4, in
from .models import MyichiTickers
Hello,
you should remove the sys.path.append() line, and use from .models import
MyichiTickers.
Also, it seems that you are writing a custom python script instead of
implementing it in your project. If I were you, I would create a
django-admin command, so it would work like
python manage.py hist
Hi There,
For various reasons I recently started efforts to covert an existing .php
application to pyhton + django.
There are quite a few scripts that are executed through cron and so from
the command line while coding.
I did find some info on how to setup the start of the script, but keep
run
Just find the location of the django folder using :
$ python -c "import syssys.path = sys.path[1:]import
djangoprint(django.__path__)"
Then dig into it to find the admin/template folder !
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To un
7 matches
Mail list logo
