Re: [XeTeX] DVIasm

2016-02-09 Thread Philip TAYLOR
Hallo Khaled -- Khaled Hosny wrote: There are many other Python 3 incompatibilities in the code (this being Python, you will not encounter them until the code in question is actually being executed, which can be deceiving). Regards, Khaled Yes, I fully appreciate that; all I was trying to

Re: [XeTeX] DVIasm

2016-02-09 Thread Khaled Hosny
On Mon, Feb 08, 2016 at 07:37:43AM +, Philip Taylor wrote: > P.S. Experimenting against both versions, I found that what Python 3 > detected as syntax errors in the Version 2 source prevented the test > from ever being evaluated, but the following three changes allow the > diagnostic to be

Re: [XeTeX] DVIasm

2016-02-09 Thread maxwell
On 2016-02-09 08:22, Wilfred van Rooijen wrote: There are many "gotchas" going from Python 2 to Python 3 - with the change from "print" to "print()" being by far the most irritating (and the most stringently enforced by the Python interpreter). There are several IDEs which can highlight problems

Re: [XeTeX] DVIasm

2016-02-09 Thread Wilfred van Rooijen
There are many "gotchas" going from Python 2 to Python 3 - with the change from "print" to "print()" being by far the most irritating (and the most stringently enforced by the Python interpreter). There are several IDEs which can highlight problems and give tips to migrate from Python 2 to