Re: Django model for non web applications

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJVlre3AAoJEC0ft5FqUuEhfe4P+wTjNKLYiAdBvzfJjJfYzG6v
s2Mc1K0IGyuIxFpMWSLCHuZRJrBNv8w6JkaJL8EC2jNxb0sUDcQt+mOAojp059fq
nocamprkWvfIHZsrsjEbmz7I3mnPpsALsK7MpM42I1fj1xsTF033Gq+UHnmSFK4s
Ung0lGlXy6nsrTVSWh4wVAEbjvMJdpV+ZYaob/r/OhLMOnM4vQMwMdnYmkSHYxIF
BE5PoXNiqnyutCxCpeQAUkbyteBt67DgqIxQFnuKDGfMAh33HunMCCKby1Bps5nG
lJxbLl6izj9Z+mgLF83LuCZxrF7BTiAX5hF+noMNB/2qpZSfOTFaGDkUyL5ptyjr
P5sOG9WoWj8tA/pUkPH5rwhnJOEJwuP0F11FgNzJYQ3dYiFIWTt4ChhYNZogR5GL
kJuGTSJI30LvMFkxDuUxZ054oCDWHnya2yWpuU4K0N5WurvIf8KeQLZuhgDi/mqB
4jZvwIQzO2dUP+e8324kwzi0NBj8qkEb/79E9iKRgVYz/cm5nE6LCvXgfpg7bfQw
QczWKzfq87xZU48JJzz64Pgd8bnJuHUme04RYM2NWdhRN1GABospNfHpEVTD613B
kLDzlRBeqzBjDd5CeSJjuH0m74j4OP9V99SRNjKf8Lw7nyIrfJ4PJi0HJVWnVdLr
YBfI3H5bP0+rLZIIVlLf
=fPUd
-----END PGP SIGNATURE-----
On 07/03/2015 07:46 AM, Vernon D. Cole wrote:
> Jeff:
> I think that Russell's answer might be more appropriate for your use
> case than Carl's. django.setup() calls settings.configure(), but also
> tries to pull in other application modules, which you might not want.

No, `settings.configure()` and `django.setup()` are not alternatives.
They are _both_ needed for Jeff's use case (depending on how he wants to
handle settings). `settings.configure()` is one option for settings;
`django.setup()` is required no matter what (since Django 1.7).

Settings can be handled either via the usual Python settings module, in
which case the DJANGO_SETTINGS_MODULE env var needs to be set to the
import path to this module, or they can be handled by calling
`settings.configure()` with a dict of the desired settings.

One of those two things needs to be done before calling
`django.setup()`. `setup()` does not "call settings.configure()" - it
loads settings, which requires either that `settings.configure()` has
already been called, or that DJANGO_SETTINGS_MODULE is set.

And yes, `django.setup()` also loads installed applications. Since
Django 1.7, this is required in order to use the ORM (which is the core
of Jeff's use case).

Carl

>
>
> On Thursday, July 2, 2015 at 6:50:20 PM UTC-6, Carl Meyer wrote:
>
> On 07/02/2015 05:49 PM, Russell Keith-Magee wrote:
> >
> > On Thu, Jul 2, 2015 at 12:50 AM, Jeff Fritz <jeff...@gmail.com
> <javascript:>
> > <mailto:jeff...@gmail.com <javascript:>>> wrote:
> >
> > I'm fairly new to Django and making my way through the tutorial.
> >
> > Knowing what I've learned so far, I'd like to explore using
> > django.db.models.Model in a non-web application. I'd like to take
> > the entire model layer and use it for database access in a
> > standalone, multithreaded python 3.4 application. It is not a web
> > application. I would like to be able to take advantage of the
> > migration capabilities in manage.py.
> >
> > Questions:
> >
> > 1. Is it as simple as adding `from djanago.db import models`?
> Would
> > this bring in any unnecessary django packages/modules,
> considering I
> > will not be developing a web application, not using views,
> > templating, etc?
> >
> >
> > It's *almost* this simple - you will also need to configure your
> Django
> > environment before you start making database calls. If you're
> looking to
> > do this in a *completely* "non-web" way, this probably means a
> call to
> > settings.configure(); details here:
> >
> > https://docs.djangoproject.com/en/1.8/topics/settings/
> <https://docs.djangoproject.com/en/1.8/topics/settings/>
>
> Don't forget that in Django 1.7+ you also need to call django.setup()
> yourself, if using Django outside the context of a WSGI server or
> management command:
> https://docs.djangoproject.com/en/1.8/ref/applications/#django.setup
> <https://docs.djangoproject.com/en/1.8/ref/applications/#django.setup>
>
> Carl
>
> >
> >
> > 2. Is the django model layer thread safe? Specifically, when
> using
> > sqlite3 as a back end?
> >
> >
> > It should be - after all, web servers are frequently multi-threaded.
> > SQLite3's performance under multithreading, however, might leave
> > something to be desired.
> >
> >
> > 3. Are there other clean ORM/database model layer
> > frameworks/packages that I should consider for python 3.4?
> >
> >
> > The other obvious candidate would be SQLAlchemy; it's a perfectly
> fine
> > ORM - without any of the other web framework overhead. It's a lot
> more
> > like a "SQL building toolkit" than Django's ORM - whether this is
> a good
> > or bad thing depends on your own preferences and use case.
> >
> > Yours,
> > Russ Magee %-)
>
> --
> You received this message because you are subscribed to the Google
> Groups "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to django-users+unsubscribe@googlegroups.com
> <mailto:django-users+unsubscribe@googlegroups.com>.
> To post to this group, send email to django-users@googlegroups.com
> <mailto:django-users@googlegroups.com>.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/05d20585-bf6e-4c1f-8014-2ea19e2d7aa0%40googlegroups.com
> <https://groups.google.com/d/msgid/django-users/05d20585-bf6e-4c1f-8014-2ea19e2d7aa0%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/5596B7B6.9060100%40oddbird.net.
For more options, visit https://groups.google.com/d/optout.