My Django Roadmap Ideas

paulox.net

2 points·pauloxnet··8 comments

Indicative of how marvelously stable Django is that none of these roadmap items have to do with the software.

I came back to the old workhorse for some experimentation recently and was delighted, delighted (!), I tell you, at how familiar, comfortable, and productive it was.

Started exploring a Turbolinks/Turboframes implementation (https://github.com/hotwire-django/turbo-django) that Just Worked. Amusingly, mid-hack, the repo owner marked it as unmaintained.

But it works! Nothing needs doing! Another victim of the cult of constant improvement.

Thanks for your feedback. I confirm Django is very stable but we're trying to constantly improve it too. See for example the Release Notes https://docs.djangoproject.com/en/stable/releases/

Do you think anything from this roadmap is going to show up in the release notes?

I think so. But of course it would require times to be selected, prioritized and deployed before that.

One I would like to see is for dj-database-url (https://github.com/jazzband/dj-database-url) to be built-into the project. It is one of those extensions I am always going to install because it is just so handy.

I agree with you. Someone already proposed it in the past but can be proposed again.

To be explicitly clear, I think you could strip out the environment variable loading stuff. Really just want there to be a standardized database url format parser. Does a lot to encourage not keeping database configuration in settings.py if there is a guided path to loading the secret.

I've added four new ideas to my list of possible improvements for Django and its community. I'd like to know what you think. https://www.paulox.net/2024/01/19/my-django-roadmap-ideas/

Reply on news.ycombinator.com