➜
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.
Created on 2014-06-25 08:51 by orsenthil, last changed 2022-04-11 14:58 by admin.
| Messages (3) | |||
|---|---|---|---|
| msg221537 - (view) | Author: Senthil Kumaran (orsenthil) *  |
Date: 2014-06-25 08:51 | |
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 what is sent and received. b) tests in that main method should be killed. c) All references in the stdlib should be updated. |
|||
| msg221545 - (view) | Author: R. David Murray (r.david.murray) * |
Date: 2014-06-25 12:51 | |
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 the 'string' method name still works :) |
|||
| msg234302 - (view) | Author: Martin Panter (martin.panter) * |
Date: 2015-01-19 05:58 | |
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. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:05 | admin | set | github: 66068 |
| 2015-01-19 05:58:33 | martin.panter | set | nosy:
+ martin.panter messages: + msg234302 |
| 2014-06-25 12:51:59 | r.david.murray | set | messages: + msg221545 |
| 2014-06-25 08:51:10 | orsenthil | create | |