Idea

I know this may not be necessary at the moment because we are comfortable depending on front-end frameworks, but I have my two ideas here: 1. what if django alone without any framework can be used to design progressive web apps, with routers that do not reload the page, we currently have one

Django Sockets Proposal

What if in django, we have a uniform way of handling server-side web sockets, built-in, not relying on external libraries? Django Channels would be a deal, but they are broad and endup making us forget about the sockets alone, what-if? we have a way of emitting those events which can be

Re: deconstruct returns 3-tuple?

That documentation is for serializing classes. There's a note box that says, "This return value is different from the deconstruct() method for custom fields which returns a tuple of four items."

Re: deconstruct returns 3-tuple?

As the note in that section explains, that is for custom *classes*, not for custom *fields*. Your observation is correct when applied to field deconstruction methods, but not for the system talked about there which lets you do it for arbitrary classes (as part of the values in field

deconstruct returns 3-tuple?

Hi, before I issue a bugreport, I'll ask here first. On https://docs.djangoproject.com/en/3.2/topics/migrations/#adding-a-deconstruct-method I can read that deconstruct() returns a 3-tuple. When I see the code in django.db.models.fields.__init__.py, Field.deconstruct() does a return