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 (self.name, path, [], keywords)
This is a 4-tuple, and even the clone() method written after it calls it
with
name, path, args, kwargs =self.deconstruct()
So, is 3.2 documentation here on a <1.9 status? Am I understanding
something not correctly?
Thanks,
Christian
--
Dr. Christian González
https://nerdocs.at
--
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/84db36b4-dc6a-fcc7-28e4-4810d152d2fb%40nerdocs.at.
