John Machin wrote:
On Feb 25, 12:00 am, Peter Otten __pete...@web.de wrote:
John Machin wrote:
Your Python 2.x code should be TESTED before you poke 2to3 at it. In
this case just trying to run or import the offending code file would
have given an informative syntax error (you have
On Feb 23, 7:47 pm, Frank Millman fr...@chagford.com wrote:
Hi all
I don't know if this counts as a bug in 2to3.py, but when I ran it on my
program directory it crashed, with a traceback but without any indication of
which file caused the problem.
[traceback snipped]
UnicodeDecodeError:
John Machin wrote:
On Feb 23, 7:47 pm, Frank Millman fr...@chagford.com wrote:
Hi all
I don't know if this counts as a bug in 2to3.py, but when I ran it on my
program directory it crashed, with a traceback but without any indication
of which file caused the problem.
[traceback snipped]
John Machin sjmac...@lexicon.net wrote:
On Feb 23, 7:47 pm, Frank Millman fr...@chagford.com wrote:
[snip lots of valuable info]
The issue is not that 2to3 should handle this correctly, but that it
should
give a more informative error message to the unsuspecting user.
Your Python 2.x code
Peter Otten __pete...@web.de wrote
John Machin wrote:
Your Python 2.x code should be TESTED before you poke 2to3 at it. In
this case just trying to run or import the offending code file would
have given an informative syntax error (you have declared the .py file
to be encoded in UTF-8 but
On 2/24/2011 8:11 AM, Frank Millman wrote:
future I will run some tests when betas are released, just in case I
come up with something.
Please do, perhaps more than once. The test suite coverage is being
improved but is not 100%. The day *after* 3.2.0 was released, someone
reported an
On Feb 25, 12:00 am, Peter Otten __pete...@web.de wrote:
John Machin wrote:
Your Python 2.x code should be TESTED before you poke 2to3 at it. In
this case just trying to run or import the offending code file would
have given an informative syntax error (you have declared the .py file
to
Hi all
I don't know if this counts as a bug in 2to3.py, but when I ran it on my
program directory it crashed, with a traceback but without any indication of
which file caused the problem.
Here is the traceback -
Traceback (most recent call last):
File C:\Python32\Tools\Scripts\2to3.py,
