#29814: Migrations deconstructing NoneType
-------------------------------------+-------------------------------------
Reporter: Daanvdk | Owner: nobody
Type: Bug | Status: new
Component: | Version: 2.1
Migrations | Keywords: migration
Severity: Normal | deconstruct nonetype none
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-------------------------------------+-------------------------------------
When in a deconstructible class used in a migration one of the arguments
to instantiate the class is the `NoneType` (aka `type(None)`) this is just
serialized as `NoneType` which will throw a NameError because it is not
defined. The only way to get this value in Python 3 is with `type(None)`
so simply serializing `NoneType` as `type(None)` should already do the
trick.
--
Ticket URL: <https://code.djangoproject.com/ticket/29814>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.107fe0908d989554b8d6a2c86dcbbf30%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
