Message242738
| Author |
r.david.murray |
| Recipients |
Devin Jeanpierre, docs@python, r.david.murray |
| Date |
2015年05月07日.22:51:21 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1431039081.3.0.401648322698.issue24144@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
No, actually, using codecs would be the most straightforward way to achieve portability. The usual way to get hex in python2 was encode('hex'), which uses the codec. But if you want to use hexlify instead, I don't see any reason not to. There's no reason to change the binascii module description, though, since it is talking about normal code, not 2/3 shared source code (where you do sometimes have to jump through somewhat awkward hoops).
(The One Obvious Way starting with 3.5 will be b'abcde'.hex(), but of course that isn't python2 compatible.) |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2015年05月07日 22:51:21 | r.david.murray | set | recipients:
+ r.david.murray, Devin Jeanpierre, docs@python |
| 2015年05月07日 22:51:21 | r.david.murray | set | messageid: <1431039081.3.0.401648322698.issue24144@psf.upfronthosting.co.za> |
| 2015年05月07日 22:51:21 | r.david.murray | link | issue24144 messages |
| 2015年05月07日 22:51:21 | r.david.murray | create |
|