Django 3.2
djangoproject.com
Django 3.2
1–10 of 195 posts
Re: Django 3.2
#2Full release notes: https://docs.djangoproject.com/en/3.2/releases/3.2/
Re: Django 3.2
#3I 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/
Re: Django 3.2
#4Maybe I'm wrong?
Re: Django 3.2
#5I'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
#6I'm more if a flask man myself. Worked with django only when I had to. Maybe I'm wrong?
Re: Django 3.2
#7I'm more if a flask man myself. Worked with django only when I had to. Maybe I'm wrong?
Re: Django 3.2
#8I'm more if a flask man myself. Worked with django only when I had to. Maybe I'm wrong?
Re: Django 3.2
#9I'm more if a flask man myself. Worked with django only when I had to. Maybe I'm wrong?
No need to reinvent the universe for bigger jobs.
Re: Django 3.2
#10I'm more if a flask man myself. Worked with django only when I had to. Maybe I'm wrong?