Puling together a few things:

On Jul 18, 2019, 3:13 PM -0400, Kevin Grinberg <[email protected]>, 
wrote:
> I've more commonly found myself using pypi.org/project/dsnparse/ more often
> than dj-database-url, due to support for DSNs in setting CACHES (with Heroku 
> Redis
> for example, you get a REDIS_URL exposed the same way).

On Jul 18, 2019, 3:32 PM -0400, Raffaele Salmaso <[email protected]>, wrote:
> I'm working on https://github.com/django/django/pull/10786 which is an
> "evolution" of dj-database-url which handle more settings types (by default
> even the email settings, but it is possible to handle any other type).
> I'll happy to finish it.

On Jul 18, 2019, 3:49 PM -0400, Jani Tiainen <[email protected]>, wrote:
> Apparently there has been few attempts to integrate dj-database-url or
> some other url parser.
> But what happened to them since so far none of them were completed?

I suspect this is a "good enough is good enough" situation. Something like what
Raffaele is talking about, or dsnparse, or whatever would probably be ideal. And
for something to be merged into core, I think it'd need to be a more full
solution than just dj-database-url.

But, because dj-database-url is Good Enough, it's pretty popular, and that sucks
away some of the impetus to work on something better.

That said: were 10786 (or similar) to be merged into core, I'd think the best
thing to do wth dj-database-url would be to put it into maintenance mode, and
just fix serious issues until all of the supported version of Django have the
new thing.

I think that's somewhat unrelated to whether it becomes an official project --
just as easy to deprecate django/dj-database-url as it is to deprecate
jacobian/dj-database-url. But happy to make that an explicit caveat for
official-dom: if something better lands in core, I'd look to deprecate
and migrate.

Jacob

-- 
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 [email protected].
To post to this group, send email to [email protected].
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/7f9457fa-9589-4cc0-a664-0b35d758927b%40Spark.
For more options, visit https://groups.google.com/d/optout.

Reply via email to