News for hackers. Stuff that matters.

A comment on Automated Python 2 to 3 code translation. Parent comment

Re:Automated Python 2 to 3 code translation by tyingq on Thursday August 17, 2017 @11:37AM (#15037705)
Sure...that's a different thing though. Python 3's choice to introduce new types and change behavior of existing types means no automated tool can really decide what to do.

The snippet I posted is a little different in that it runs on both Python 2 as well as 3, but the 2to3 tools choke on it.

[ Parent | on HN ]
Re:Automated Python 2 to 3 code translation by eesmith on Thursday August 17, 2017 @01:36PM (#15038930)
Ahh, yes, you're right.

I'm still irritated by this specific case because my code and documentation used s.encode("hex") often, and it took a while to fix them all. Especially as the original code used both str and unicode hex-encoded values, so I couldn't drop in binascii. I ended up adding a C extension function.

[ Parent | on HN ]