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 JustAnother1, barry, david__, giampaolo.rodola, r.david.murray, taleinat
Date 2018-06-14.13:54:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1528984471.57.0.947875510639.issue29750@psf.upfronthosting.co.za>
In-reply-to
Content
While you are correct that latin1 may be common in this situation, I think it may still be better to have utf-8 be the default, since that is the (still emerging? :) standard.  However, you are correct to call for examples: if in the *majority* of the real-world cases it turns out latin1 is what is used, then we could default to that (or not have a default, but instead document our observations).

I don't know how we accumulate enough information to make that decision, though.  Maybe we could look at what other mail programs do?  Thunderbird, etc?  David, which mail program(s) did you use that were able to successfully send that password?

And yes, by binary passwords I mean that the module needs to support being passed a bytes-like object as the password, since clearly there are servers "in the wild" that support non-ascii passwords and the only way to be sure one can send the server the correct password is by treating it as a series of bytes.  The library caller will have to be responsible for picking the correct encoding based on local knowledge.
History
Date User Action Args
2018-06-14 13:54:31r.david.murraysetrecipients: + r.david.murray, barry, taleinat, giampaolo.rodola, david__, JustAnother1
2018-06-14 13:54:31r.david.murraysetmessageid: <1528984471.57.0.947875510639.issue29750@psf.upfronthosting.co.za>
2018-06-14 13:54:31r.david.murraylinkissue29750 messages
2018-06-14 13:54:31r.david.murraycreate