#16291: Document that TypedChoiceField does not coerce empty_value
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
vanschelven | Status: closed
Type: | Component: Documentation
Cleanup/optimization | Severity: Normal
Milestone: | Keywords:
Version: 1.3 | Has patch: 1
Resolution: fixed | Needs tests: 0
Triage Stage: Ready for | Easy pickings: 1
checkin |
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Comment (by taavi223):
Replying to [comment:4 julien]:
> Thank you for your patch.
>
> Just a note on the process. As mentioned in a few places in the
contributing guide (for example, at the bottom of `[1]`), one should not
promote their own patch to RFC and instead let someone else review the
patch first. Then the ticket can be moved by that person to RFC otherwise
comments can be left telling how the patch should be improved.
>
> In this case, the patch looks good so I'm leaving the ticket in RFC.
Don't hesitate to check out the contributing guide for more info on how to
deal with future tickets. Cheers!
>
> `[1]` https://docs.djangoproject.com/en/dev/internals/contributing
/triaging-tickets/
Whoops. Sorry about that. I looked through the docs the other day, but I
was just skimming them and I somehow missed that. Maybe that's something
I should add to my tutorial for first time contributors. :-)
--
Ticket URL: <https://code.djangoproject.com/ticket/16291#comment:6>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
