Week ending August 28, 2022
*Triaged: *
https://code.djangoproject.com/ticket/33954 - NaN can be stored in
DecimalField but cannot be retrieved (accepted)
https://code.djangoproject.com/ticket/33955 - AttributeError in
admindocs ViewDetailView (accepted)
https://code.djangoproject.co
Week ending August 21, 2022
*Triaged: *
https://code.djangoproject.com/ticket/33925 - Testing tools Management
Commands example fails (invalid)
https://code.djangoproject.com/ticket/33916 - Support for serialization
of combination of Enum flags. (accepted)
https://code.djangoproject.
That helps, thanks.
I don't think it's worth it either, because, ultimately, it'll still be
"wrong". The right __module__ is wherever you called modelform_factory from.
The perils of meta programming...
On Monday, August 29, 2022 at 11:33:50 AM UTC+2 j.bre...@netzkolchose.de
wrote:
> Looks to
Looks to me like being carried forward from the very first metaclass
``MediaDefiningClass``, which happens to be defined in django.forms.widgets.
Should be fixable by explicitly adding a __module__ notion to type().
Not sure though if it is worth additional code just for the sake of
pretty __m
Hi all,
Not quite sure if this is the right forum, but it concerns Django itself
and static analysis of it.
I'm working heavily on static analysis of the Django code base, including
mypy and Django-stubs.
For the life of me, I cannot figure out why the class returned by
modelform_factory has
