➜

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 r.david.murray
Recipients r.david.murray, sdaoden, torsten.becker
Date 2011-04-13.22:02:22
SpamBayes Score 0.0013979132
Marked as misclassified No
Message-id <1302732142.93.0.537615932331.issue11783@psf.upfronthosting.co.za>
In-reply-to
Content 
Yes, putting the function in _parseaddr is fine.  And yes, 232 looks like a good place.  The alternative would be understanding the rfc822 parser, which is pretty mind bending, and of doubtful additional benefit.  (At most it would save a pair of split/join calls.)
History
Date User Action Args
2011-04-13 22:02:23r.david.murraysetrecipients: + r.david.murray, sdaoden, torsten.becker
2011-04-13 22:02:22r.david.murraysetmessageid: <1302732142.93.0.537615932331.issue11783@psf.upfronthosting.co.za>
2011-04-13 22:02:22r.david.murraylinkissue11783 messages
2011-04-13 22:02:22r.david.murraycreate