#36524: EmailMessage method documentation cannot be cross referenced
-------------------------------------+-------------------------------------
Reporter: Mike Edmunds | Owner: Mike
Type: | Edmunds
Cleanup/optimization | Status: assigned
Component: Core (Mail) | Version: 5.2
Severity: Normal | Resolution:
Keywords: email | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Natalia Bidart):
Replying to [comment:4 Mike Edmunds]:
> Replying to [comment:2 Natalia Bidart]:
> > (Arguably we should consider splitting the `ref` part of the
topics/email.txt docs into its own ref file.)
>
> Oh my yes! And perhaps split out separate chapters for:
> - ''using'' email: common settings to get email working; composing and
sending messages
> - ''extending'' email: developing custom EmailBackends, etc.
>
> (But that seems like a larger discussion.)
I think that a base split of ref/non-ref would certainly be in the scope
of this ticket. Then, how the remaining bits in the topics/email.txt are
organized could be evaluated when the file is cleaned up. Perhaps would a
couple of top-level sections suffice?
Looking forward to your ideas!
--
Ticket URL: <https://code.djangoproject.com/ticket/36524#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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701983d79c39f-7537aeb6-52bc-492e-9244-27363bf15edf-000000%40eu-central-1.amazonses.com.
