#32933: Point users to BoundField.initial instead of Form.get_initial_for_field() -------------------------------------+------------------------------------- Reporter: Chris Jerdonek | Owner: Chris Type: | Jerdonek Cleanup/optimization | Status: closed Component: Documentation | Version: dev 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 Carlton Gibson <carlton.gibson@…>): In [changeset:"aace6c531d5b03b023516b244d87cf5608e24d90" aace6c53]: {{{ #!CommitTicketReference repository="" revision="aace6c531d5b03b023516b244d87cf5608e24d90" [3.2.x] Fixed #32933 -- Documented BoundField.initial as preferred over Form.get_initial_for_field(). Backport of 6559a55eed09780b30ee3c3636ccf30318622bcf from main }}} -- Ticket URL: <https://code.djangoproject.com/ticket/32933#comment:12> 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 django-updates+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/067.4dd671b19bc260f37e45182e5ccf8688%40djangoproject.com.