Ahh typo, my previous message is about week ending November 24, 2019.
--
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 djan
Week ending December 1, 2019.
*Triaged:*
https://code.djangoproject.com/ticket/31029 - Link to more specific
sections when using the :rfc: role. (accepted)
https://code.djangoproject.com/ticket/31027 - Prefer DOM object properties
over Element.getAttribute() and Element.setAttribute(). (accepted
As document says,
https://docs.djangoproject.com/en/2.2/ref/models/fields/#booleanfield
previously
blank=True was implicit but in django 2.1+ , we have to add it externally.
So i dont understand why new migrations are coming up for this? Does this
mean that previously blank=True wasnt consider
Hi,
I am wondering if Django shouldn't use Unicode Plural Rules as standard and
promote it for third-party apps. Even if sometimes number of forms are not
applicable to certain cases, there may be cases when all of forms will be
needed.
Especially if implementing having different plural rules for
On Thu, Dec 5, 2019 at 4:23 PM Maciek Olko wrote:
> Hi,
> I am wondering if Django shouldn't use Unicode Plural Rules as standard
> and promote it for third-party apps. Even if sometimes number of forms are
> not applicable to certain cases, there may be cases when all of forms will
> be needed.
