Re: Integrate dj-database-url into Django
I'd love to see native dj-database-url support in Django. I suppose it
would have to support all the back-ends, no? It might lead to confusion
otherwise.
On 0, gw...@fusionbox.com wrote:
I'd like to approach this as 'support database urls in django', rather
than 'copy/paste dj-database-url into django'. For postgres (I'm not sure
about other backends), a database url can be passed directly to psycopg2.
The postgres connection string format actually supports more features than
is possible with django's HOST/USER/PORT... style settings. For example,
you can pass multiple hosts and psycopg2 will attempt to connect to one of
them: https://paquier.xyz/postgresql-2/postgres-10-multi-host-connstr/.
Any attempt to parse the url in django will result in a loss of those
features.
The only problem I see is that we have to parse the database backend out
of the url, and you can't pass a url like 'postgis://' to psyscopg2.
I'd like to be able to do something like:
DATABASES = {
'default': {
'DSN': 'postgres://',
'ENGINE': 'django.contrib.gis.db.backends.postgis',
},
}
And let psycopg2 handle the DSN.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to [1]django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to
[2]django-developers@googlegroups.com.
Visit this group at [3]https://groups.google.com/group/django-developers.
To view this discussion on the web visit
[4]https://groups.google.com/d/msgid/django-developers/38553bb5-59b0-4772-a17a-282f795f1548%40googlegroups.com.
For more options, visit [5]https://groups.google.com/d/optout.
References
Visible links
1. mailto:django-developers+unsubscr...@googlegroups.com
2. mailto:django-developers@googlegroups.com
3. https://groups.google.com/group/django-developers
4.
https://groups.google.com/d/msgid/django-developers/38553bb5-59b0-4772-a17a-282f795f1548%40googlegroups.com?utm_medium=email&utm_source=footer
5. https://groups.google.com/d/optout
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/20180728075639.b6i5dzhund3g2xfv%40lostatsea.lostatsea.
For more options, visit https://groups.google.com/d/optout.
Re: Type hints, PEP 561, and mypy-django
FYI we're chatting on https://gitter.im/mypy-django/Lobby about organising this. Feel free to drop by there. On 0, Luke Murphy wrote: Hi folks, Following a short discussion over at: https://github.com/machinalis/mypy-django/issues/9, There is some renewed interest in getting stuck into type hints for Django. I wanted to drop a mail here to see what the status is. In preparation for this email, I've been combing the Django issue tracker and some related project Github issues to see what has already been done and adding notes over at: https://github.com/lwm/mypy-django/issues/1 Was I correct in discovering that there is some general consensus on waiting PEP 561 to land? It seems like that PEP has been accepted and there are three options for implementation: PEP 561 notes three main ways to distribute type information. The first is a package that has only inline type annotations in the code itself. The second is a package that ships stub files with type information alongside the runtime code. The third method, also known as a “stub only package” is a package that ships type information for a package separately as stub files. I saw mention of the necessity of DEP being submitted. Has it been done yet or started? I can't see anything related over at: https://github.com/django/deps Hope someone can enlighten me, thanks! Best, Luke -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20180722111916.xvbjtbxs7d2zu6jy%40lostatsea.lostatsea. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20180723075146.qsz2sa2tbg2wbldl%40lostatsea.lostatsea. For more options, visit https://groups.google.com/d/optout.
Type hints, PEP 561, and mypy-django
Hi folks, Following a short discussion over at: https://github.com/machinalis/mypy-django/issues/9, There is some renewed interest in getting stuck into type hints for Django. I wanted to drop a mail here to see what the status is. In preparation for this email, I've been combing the Django issue tracker and some related project Github issues to see what has already been done and adding notes over at: https://github.com/lwm/mypy-django/issues/1 Was I correct in discovering that there is some general consensus on waiting PEP 561 to land? It seems like that PEP has been accepted and there are three options for implementation: PEP 561 notes three main ways to distribute type information. The first is a package that has only inline type annotations in the code itself. The second is a package that ships stub files with type information alongside the runtime code. The third method, also known as a “stub only package” is a package that ships type information for a package separately as stub files. I saw mention of the necessity of DEP being submitted. Has it been done yet or started? I can't see anything related over at: https://github.com/django/deps Hope someone can enlighten me, thanks! Best, Luke -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20180722111916.xvbjtbxs7d2zu6jy%40lostatsea.lostatsea. For more options, visit https://groups.google.com/d/optout.
