Thx

Is there any way to NOT “translate” some parts of my code ? I’m using the struct module, and it doesn’t like the string to unicode translation (‘…’ to u’…’ I mean), because it needs real ascii string.

I don’t have much time to read your code and understand it, because I’m already crossing the deadline of my work, so I will correct by hand the wrong parts for the moment.

It gives me:
ushort = Struct(u’<H')
TypeError: Struct() argument 1 must be string, not unicode

Thx for your work, and sorry for my english

PS: I cooked a cludgy module to make my code work under python2 with 2to3, to use it I add the line "from compat import *" at the beginning of my modules. Here it is:

compat.py
—
# Compatibility for Python 2 & 3
# open (compat_open) and re.compile (compat_regexp)

import sys
import re

if sys.version_info[0] == 3:

import builtins

__builtin__ = builtins

def open(filename, mode='r'):
return __builtin__.open(filename, mode, encoding='utf-8', newline='')

def re_compile(pat, flags=None):
if flags is not None: return re._compileorig(pat, flags)
else: return re._compileorig(pat)

else:

from future_builtins import *
import codecs
import __builtin__

def open(filename, mode='r'):
return codecs.open(filename, mode, encoding='utf-8')

def re_compile(pat, flags=0):
return re._compileorig(pat, flags|re.UNICODE)

#__builtin__.__open_orig = __builtin__.open
#__builtin__.open = _compat_open

re._compileorig = re.compile
re.compile = re_compile

Feedback coming soon.

The plan is to gently alter the surrounding namespace, not clobber it

There is a specification outlined in the trunk, but the basic idea is this:
a, b, c, *d, e, f, g, h = range(100)

fixes to

_3to2list = list(range(100))
a, b, c, d, e, f, g, h = _3to2list[:3] + [_3to2list[3:-4]] + _3to2list[-4:]

and this:
for a, b, c, *d, e, f in some_thing:
do_stuff

fixes to

for _3to2iter in some_thing:
_3to2list = list(_3to2iter)
a, b, c, d, e, f = _3to2list[:3] + [_3to2list[3:-2]] + _3to2list[-2:]
do_stuff

Please, though, let me know if there are any cases where this fix would be incorrect!

Joe, thanks for picking this up. I still wonder how you can syntactically fix the Py3 code to Py2 without clobbering the surrounding namespace. But I’ll stay tuned to find out