[issue21869] Clean up quopri, correct method names encodestring and decodestring

2015-01-18 Thread Martin Panter
Martin Panter added the comment: Personally I don’t have a problem with the names; I would consider str(), bytes(), bytearray() types all to be “strings”. However there is precedent in the “base64” module for renaming to en/decodebytes(); see Issue 3613. -- nosy: +vadmium

[issue21869] Clean up quopri, correct method names encodestring and decodestring

2014-06-25 Thread R. David Murray
R. David Murray added the comment: Well, it's not actually obvious that this should be done. Or, at least, it is not obvious the old methods should be dropped. I think we had this same discussion about a similar method in ElementTree. I don't remember the outcome except that I'm pretty sure

[issue21869] Clean up quopri, correct method names encodestring and decodestring

2014-06-25 Thread Senthil Kumaran
New submission from Senthil Kumaran: issue15588 brought the topic that quopri has ancient methods like encodestring, decodestring, which a user might expect that will send a string, but instead has to send bytes. This needs to be cleaned up. a) function name should be accurate and represent