Fellow Reports - May 2023
Week ending May 7, 2023 Released Django 4.2.1, 4.1.9, and 3.2.19. *Triaged:* https://code.djangoproject.com/ticket/34528 - Reduce Add/RemoveIndex migration operations. (created) https://code.djangoproject.com/ticket/34529 - Squashing migrations with Meta.index_together -> indexes transition should remove deprecation warnings. (created) https://code.djangoproject.com/ticket/34069 - get_language_from_request should not fallback to settings.LANGUAGE_CODE (duplicate) https://code.djangoproject.com/ticket/34532 - Form.default_renderer is ignored in formsets. (accepted) https://code.djangoproject.com/ticket/34534 - Reduce index/constraints operations. (accepted) https://code.djangoproject.com/ticket/34537 - Add an User inline to the default GroupAdmin (duplicate) https://code.djangoproject.com/ticket/34538 - Incorrect query generated with on subquery WHERE depending on the order of the Q() objects (duplicate) https://code.djangoproject.com/ticket/34541 - StorageRouter (wontfix) https://code.djangoproject.com/ticket/34525 - index_together warning after migration to new style (invalid) https://code.djangoproject.com/ticket/34543 - Thousand separator breaking templates (needsinfo) https://code.djangoproject.com/ticket/34544 - DBMS_LOB.SUBSTR() is unnecessary for "IS NULL" condition on Oracle. (accepted) https://code.djangoproject.com/ticket/34545 - Typo in "FAQ: Installation". (accepted) *Reviewed/committed:* https://github.com/django/django/pull/16809 - Fixed #33759 -- Avoided unnecessary subquery in QuerySet.delete() with self-referential subqueries if supported. https://github.com/django/django/pull/16816 - Fixed #34513 -- Added system check for relational fields in ModelAdmin.list_display. https://github.com/django/django/pull/16801 - Fixed #34517 -- Avoided connection post_init signal to ImageField without width/height fields. https://github.com/django/django/pull/16824 - Fixed #34535 -- Fixed SQLite dbshell crash on pathlib.Path when handling exceptions. https://github.com/django/django/pull/16827 - Removed unnecessary workarounds for Sphinx < 4.3.0. https://github.com/django/django/pull/16828 - Corrected code-block directives in docs. https://github.com/django/djangoproject.com/pull/1356 - Corrected og title and description for teams page. *Authored:* https://github.com/django/django/pull/16813 - Fixed #34523 -- Fixed TransactionManagementError in QuerySet.update_or_create() with MyISAM storage engine. https://github.com/django/django/pull/16819 - Fixed #34528 -- Reduced Add/RemoveIndex operations when optimizing migrations. https://github.com/django/django/pull/16820 - Fixed #34529, Refs #34525 -- Reduced index operations with Meta.indexes/index_together when optimizing migrations. https://github.com/django/django/pull/16826 - Fixed MultipleFileFieldTest.test_file_multiple_validation() test if Pillow isn't installed. https://github.com/django/django/pull/16829 - Refs #27236 -- Made more cosmetic edits to Meta.index_together deprecation. Best, Mariusz -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/1b6129f8-85c1-522e-8a0c-01652945a4e8%40gmail.com.
Re: Can we move the activity on this list to the Forum now?
I'm also available to do some moderation in the forum. I'll try to chase getting moderator perms to help! On Saturday, May 6, 2023 at 5:09:51 AM UTC-3 Carlton Gibson wrote: > Hey Curtis. > > The notifications settings are very flexible, and allow good filtering (to > your inbox) if that's how you want them. > > For example, I'm able to get notifications for the Django Internals > category, and the Async subcategory of Using Django (and then I'm able to > keep up with the rest just by glancing at the latest tab.) > > The water is nice 😅 > C. > > > On Thu, 4 May 2023 at 07:29, Curtis Maloney wrote: > >> Does the Forum allow me to get email notifications / summaries? >> >> If not, it will mean I disconnect with that part of the community. >> >> -- >> Curtis >> >> On Thu, 4 May 2023, at 15:19, Arthur Rio wrote: >> >> Yes please! >> >> >> >> On May 3, 2023 at 11:19:12 PM, jure.er...@gmail.com (jure.er...@gmail.com) >> wrote: >> >> >> +1 >> >> >> >> *From:* django-d...@googlegroups.com *On >> Behalf Of *natali...@gmail.com >> *Sent:* sreda, 03. maj 2023 20:10 >> *To:* Django developers (Contributions to Django itself) < >> django-d...@googlegroups.com> >> *Subject:* Re: Can we move the activity on this list to the Forum now? >> >> >> >> Hello everyone! >> >> >> >> I was wondering if we could make a decision about this topic. On the one >> hand, and as far as I understand, the forum is the preferred channel of >> communication. On the other hand, having multiple channels of communication >> can spread important discussions too thin, making it difficult to have >> productive conversations in one place. >> >> >> >> As a newcomer to the contributing community, I can attest that the >> current situation causes some confusion. IMHO, the same applies to the chat >> options: there is IRC and the Discord server (though perhaps I should start >> a new forum topic about that in order to keep decisions separated). >> >> >> >> In summary, I'm +1 to "move on-mass (all few of us :) over there"! >> >> >> >> Thank you! >> >> Natalia. >> >> On Thursday, January 26, 2023 at 10:07:36 AM UTC-3 Alex Krupp wrote: >> >> I just submitted a proposal to create a Discourse plugin to improve the >> accuracy of their inbound email parsing. This would enable two things: >> >>- Folks who prefer to live in their inbox could continue to do so and >>contribute by just replying to emails. Discourse currently has >>reply-by-email, but it often mangles formatting and/or entirely deletes >>text. Once these issues are fixed, folks who like the current experience >>would be able to just pretend the forum doesn't exist and continue having >>the same experience as they currently have with Google Groups. >>- Right now importing the archives from Google Groups into Discourse >>isn't realistic for the same reasons; some messages will import >> correctly, >>but others will be mangled or missing text. This would also be made >>possible. >> >> If this is something you care about (positively or negatively), here is >> the exploratory proposal: >> >> >> >> >> https://meta.discourse.org/t/proposed-plugin-to-improve-reply-by-email-accuracy/252944 >> >> >> >> Any feedback and/or testing would be much appreciated! Right now >> Discourse recognizes that this is a problem and is interested in solving >> it, but getting it prioritized will require folks to A) speak up saying >> they want it done B) test the underlying API to verify that it actually >> solves the problem. >> >> >> >> Alex >> >> >> >> On Fri, Jan 20, 2023 at 2:24 AM Carlton Gibson >> wrote: >> >> OK, I've updated the Trac wiki page to point to the forum too. (We use >> this as a wiki-link in responses to guide folk onwards.) >> >> >> >> The docs have a `|django-developers|` shortcut used in quite a few places >> so that needs a moment more to review and adjust. >> >> (I'll look at it soon-ish... — if no-one beats me to it :) >> >> >> >> Thanks. >> >> C >> >> >> >> On Thu, 19 Jan 2023 at 18:15, Andrew Godwin wrote: >> >> We should at least update those Trac and Triage Workflow docs to point to >> both, maybe with the Forum first? >> >> >> >> Andrew >> >> >> >> On Thu, Jan 19, 2023, at 12:30 AM, Carlton Gibson wrote: >> >> I'm trying to begin new conversations there where I can. >> >> >> >> The main issue is that we're still pointing people here from Trac and the >> Triage Workflow docs — so if there's a rough "Yeah, let's do it" we can >> adjust practice there. >> >> >> >> I expect there will always be the "How do I start?" posts. The Forum at >> least has a pinned post for that. ... >> >> >> >> On Thu, 19 Jan 2023 at 01:04, 'Kye Russell' via Django developers >> (Contributions to Django itself) wrote: >> >> Hi all, >> >> >> >> I find that the signal-to-noise ratio on this mailing list is (by my >> determination) quite bad around this time of year. >> >> >> >> Is a mov
Fellow Reports - May 2023
Week ending 2023-05-07 (week 19) Triaged: https://code.djangoproject.com/ticket/34531 - Rendering form throws deprecation warning (invalid) https://code.djangoproject.com/ticket/34539 - `get_prep_value` no longer called for JSONField (accepted with ongoing conversations) https://code.djangoproject.com/ticket/34540 - [feature request] Run FileField storage callable during runtime and not during buildtime (wontfix) https://code.djangoproject.com/ticket/34542 - Required fields not enforced when interactively using createsuperuser (invalid) https://code.djangoproject.com/ticket/34543 - Thousand separator breaking templates (needsinfo) Commented on: https://code.djangoproject.com/ticket/32827 - Squashing migrations isn't very effective in complicated projects; rewrite docs to provide a preferred manual trimming process Reviewed: https://github.com/django/django/pull/16820 - Fixed #34529, Refs #34525 -- Reduced index operations with Meta.indexes/index_together when optimizing migrations. https://github.com/django/django/pull/16822 - Update tutorial04.txt to make location of change explicit https://github.com/django/django/pull/16777 - Fixed #12780 -- Added compound form/formset validation in ModelAdmin https://github.com/django/django/pull/16592 - Fixed #30386 -- Fixed primary key quoting in admin related object links. Reviewed and landed: https://github.com/django/django/pull/16821 - Fixed #34530 -- Improved docs when customizing storage for FileField. https://github.com/django/django/pull/14499 - Refs #31369 -- Improved hint message in NullBooleanField's deprecation warning. PR Cleanup https://github.com/django/django/pull/14783 - Tab completion when executing as `./manage.py` Other/Misc: Watched and learnt from Mariusz while he released Django 4.2.1, 4.1.9 and 3.2.19. Resurfaced conversation on (completing?) migrating to the forum, still unclear how that'll continue. DjangoCon US flight tickets! :tada: -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/0cb0d6fe-fd09-4c91-b32c-9b54d8219d7bn%40googlegroups.com.
