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 ggenellina
Recipients georg.brandl, ggenellina
Date 2008-11-06.09:48:10
SpamBayes Score 0.0050307503
Marked as misclassified No
Message-id <1225964892.7.0.454643269656.issue4268@psf.upfronthosting.co.za>
In-reply-to
Content
Functions message_from_string and message_from_file are documented as 
belonging to the email.parser module, but in fact they live at the top 
of the email package.

The .rst source looks fine, but the rendered html says  
`email.parser.message_from_string`. 
http://docs.python.org/library/email.parser.html#parser-class-api

Perhaps it's the `module:: email.parser` directive at the top?

A similar problem is in email.mime.rst; all the documented classes are 
exposed at the top of the email package (i.e. should be email.MIMEBase, 
not email.mime.MIMEBase)
History
Date User Action Args
2008-11-06 09:48:12ggenellinasetrecipients: + ggenellina, georg.brandl
2008-11-06 09:48:12ggenellinasetmessageid: <1225964892.7.0.454643269656.issue4268@psf.upfronthosting.co.za>
2008-11-06 09:48:11ggenellinalinkissue4268 messages
2008-11-06 09:48:10ggenellinacreate