dj-database-url gives Django developers two main things: 1. the ability to represent their database settings via a string (a-la sqlalchemy); very useful for environmnent variables and 12factor apps. 2. it will automatically use the DATABASE_URL environment variable, if present.
I'm not sure if #2 is appropriate for Django Core (but it would be nice, as Gunicorn supports both PORT and WEB_CONCURRENCY), but I know #1 is perfect. This plan has previously been discussed (at a conference, DjangoCon EU in Zurich, long ago) and approved by JKM, before his role at Heroku, if that is helpful information. I think this change would vastly improve the usability of Django, and would be an excellent and simple move for the project. Many thanks for your consideration. <3 -- Kenneth Reitz https://code.djangoproject.com/ticket/28236 -- 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/057ced98-4471-4939-960b-900ec39f54b7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
