➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author nharold
Recipients Srujan Chaitanya, barry, docs@python, ezio.melotti, flyjwayur, maciej.szulik, mdk, nharold
Date 2016-05-31.18:50:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1464720600.49.0.6235522954.issue26176@psf.upfronthosting.co.za>
In-reply-to
Content 
emailexample.patch fixes the specific issue mentioned in #26426: the Address constructor is now used as documented.  It changes the final output of the two combined examples (as presented in the documentation) accordingly.

In general it seems as though these examples (the two in in 19.1.14.1) were meant to be read, not run.  To run them, the user would have to supply (1) their own roasted-asparagus.jpg, (2) their own local SMTP server, and (3) their own implementation of imaginary.magic_html_parser.  However, the Address constructor usage issue was real, and I was able to generate the relevant output without (2) and (3).
History
Date User Action Args
2016-05-31 18:50:00nharoldsetrecipients: + nharold, barry, ezio.melotti, docs@python, maciej.szulik, mdk, Srujan Chaitanya, flyjwayur
2016-05-31 18:50:00nharoldsetmessageid: <1464720600.49.0.6235522954.issue26176@psf.upfronthosting.co.za>
2016-05-31 18:50:00nharoldlinkissue26176 messages
2016-05-31 18:50:00nharoldcreate