Live data from Hacker News

Django 3.2

djangoproject.com

1–10 of 195 posts

Re: Django 3.2

#3
post #2

I have been using version 3.2 since Beta. Deployed on a production application, so far without a single problem. I highly praise Automatic AppConfig discovery and BigAutoField for pkey. I highly recommend the transition to Django 3.2 Full release notes: https://docs.djangoproject.com/en/3.2/releases/3.2/

[deleted]

Re: Django 3.2

#5
Congratulations to the Django project and contributors on a big LTS release. And a huge thank you for the consistently excellent framework that so many have built their web dev careers on.

I'll post this as a Show HN soon, but I'll mention it now as a soft-launch introduction. After a decade of using Django I started a project I always wanted to exist: backported security and bug fixes to old versions that the Django project has dropped support for.

I've seen many Django projects eventually get stuck on an old version as the team I'm on is forced to defer upgrades in favor of commercial pressures and essential product delivery.

So you can subscribe to https://www.codestasis.com/ to stay patched on your old version, removing the urgency to upgrade. Then unsubscribe when you're caught up.

It's free for personal use and a paid subscription for businesses and organizations.

Re: Django 3.2

#8

I'm more if a flask man myself. Worked with django only when I had to. Maybe I'm wrong?

I'm more of a Django man, worked with Flask only when i had to. There's no "wrong" or "right" in this…

Re: Django 3.2

#10

I'm more if a flask man myself. Worked with django only when I had to. Maybe I'm wrong?

I also used Flask and I wasn't a Django fan. But this got me on larger projects, when Django and his "Batteries Included" made sense. Now I will soon think about the size of the project in advance, and based on that I will choose Django or Flask. There really is not something wrong here. Everything has its pros and cons.
Post reply on HN