Hi Christian,
if you like (and have enough spare time :-) ), do that! Maybe at first
only a few opcodes to see, could this work and how works it. Separate
branch or a patch isn't a problem.
Goal should be, to support python2.7 AND python3 without pain. As I
remember (it's a few months ago :-) ) the regression test was the
biggest part in transition to python3. All other should be normal work ...
And yes, the "exec" command in test_*.py files is one of such problems.
cu, Thomas
Am 04.02.2016 um 21:52 schrieb Christian Taedcke:
I will try to convert the regression tests to python 3. When i have
something, i will commit it to a separate branch.
I am not sure how we should convert the tests to unittests, but I think
it is a good idea to do that. I think it would be good to keep the
structure with a base test class and derived classes for the different
opcodes. But i think that we should drop the "exec" in the opcode tests
and use regular test classes.
_______________________________________________
Simulavr-devel mailing list
Simulavr-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/simulavr-devel
