#26702: Document custom field subclass change requires new custom field class
-------------------------------------+-------------------------------------
Reporter: baylee | Owner: baylee
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 1.9
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"5e46075fcf5dce3a846d208ab39e7f7aed7f70eb" 5e46075]:
{{{
#!CommitTicketReference repository=""
revision="5e46075fcf5dce3a846d208ab39e7f7aed7f70eb"
[1.10.x] Fixed #26702 -- Documented how to change the base class of a
custom field.
Backport of 7767978beec6098baea75d50a191a3b8224e729f from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26702#comment:10>
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/064.f4fa0e6edbc583b27c868d62b810f1db%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
