Week ending 2023-10-29 (Week 43)
I started the week feeling quite exhausted after DjangoCon US and the trip back home. I thought I could ease into the week, when Mariusz luckily reminded me (thank you!!!) that “today” (that was last Monday) was Beta Release Day. After a brief moment of panic and some mate, I reviewed and merged the pending release blocker, allowing for the subsequent 5.0 Beta Release, so it all worked out in the end.
To avoid reliving such a shocking episode, I’ve created a dedicated Google Calendar for Django Releases. The main purpose of this calendar is to track both past and upcoming Django releases, as well as send (me) timely reminders to allow sufficient preparation time for release tasks. If you believe this calendar could be valuable for you personally or for the broader community, let me know!
Triaged
- https://code.djangoproject.com/ticket/34929 - Issue with Django 3.2 and Django-storage 1.14.2 after Upgrading from Django 2.2.28 (invalid)
- https://code.djangoproject.com/ticket/33230 - Test client doesn’t set explicitly provided Content-Type when data is empty (wontfix)
- https://code.djangoproject.com/ticket/34930 - Parallel tests fail on Python 3.11+ when IsolatedAsyncioTestCase is used (wontfix)
Reviewed
- https://github.com/django/django/pull/17407 - Fixed #34923 – Avoided initializing LEVEL_TAGS when importing django.contrib.messages.
- https://github.com/django/django/pull/17370 - Fixed #34899 – Added blank choice to callable choices lazily.
- https://github.com/django/django/pull/17384 - Fixed #15578 – Stated the processing order of fixtures in the fixtures docs.
- https://github.com/django/deps/pull/81 - Update DEPs 1, 10, and 12 to reflect current governance
Other/Misc
- Django 5.0 Beta Release!
- Reading of DEPs, proposed changes and replied to https://forum.djangoproject.com/t/updating-our-dep-process-dep-1/24783/8
- DjangoCon survey.
- Security patch review.