I've more commonly found myself using https://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).
I don't think the maintainer is offering to do take dsnparse under DEP 7, so "blessed dj-database-url" may be better than the status quo, but I worry if blessing a partial solution is liable to send some folks down a less-than-ideal path (I'm imagining a new user finding dj-database-url as then "official" solution, and then getting stuck trying to wrestle with it to do "almost the same thing" with configuring CACHES). That's not to say that dj-database-url couldn't grow into a more generic DSN parser, and maybe that's the plan - in which case, enthuastically +1! But AFAICT the diffs are not altogether trivial, and I'm not presently able to volunteer to do it, so I'm working on the assumption that dj-database-url retains more or less its present scope. Kevin On Thursday, July 18, 2019 at 12:46:13 PM UTC-4, Jacob Kaplan-Moss wrote: > > Hi folks - > > I’d like to gauge interest in adopting dj-database-url > (http://github.com/jacobian/dj-database-url) as an official project > ( > https://github.com/django/deps/blob/master/final/0007-official-projects.rst > ). > This is my pre-proposal. I think dj-database-url is very widely-used, and > scratches a specific but annoying itch. Maintenance burden is minimal, but > important. > > What do other folks think? DEP 7 asks us to > > > solicit feedback from the community and work out if there is rough > agreement > > that the project is a good thing for Django to adopt, particularly > focusing on > > any alternative approaches to the same problem and the relative merits > of them, > > including code design, scalability, alignment with existing Django > design and > > philosophy, and having an available development and maintenance team. > > So - thoughts? > > I'm volunteering to be the shepherd, but do intend to form a larger team. > > I've also opened https://github.com/jacobian/dj-database-url/issues/120 > as another place for this discussion. Please feel free to comment either > place. > > [Backstory, and why this is living on my github right now. @kennethreitz > was > looking for a new maintainer, and reached out to me to see if Django might > be > interested. I thought perhaps so, and offered to take over maintainership > in the > meantime while we work through the DEP 7 process. If it turns out that an > Official Project is the wrong home for this, I'll either maintain it > long-term > or transfer it again.] > > 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/2d00b471-5408-460a-8b20-9520d2a04f07%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
