OK, I'll let you decide something on the tests. My main concern was to have something to try and make sure that I hadn't really messed up in the python3 bindings while trying to allow people to still use python2.
Michael Whapples On 15/05/2012 15:48, Mesar Hameed wrote:
Hi Michael, Attila, Thanks for the good work. Just a heads up, please dont put a lot of effort in the testing infrastructure, Christian and I are in discussion on how to best do this. We will merge the two methods of testing, to reduce duplication, please bare with us until we have something stable. Thanks. Mesar On Tue 15/05/12,15:31, Michael Whapples wrote:Attila, I have now made a runharness.py file which allows separate tests for python2 or python3. The convention goes: If the harness file is for python2 then the name should end _harness.py, if the harness file is for python3 it should end _harness_py3.py. Also I have now committed python3 versions of the actual harness tests. It is just the doctests which need to be made to work with python3. Michael Whapples On 15/05/2012 13:52, Hammer Attila wrote:Hy, I sending the runharness.py related modification to this main test script run right under Python2.7 and Python 3.2, because Michael already merged with Python3 and 2.7 bindings. This patch doesn't resolve the test harness files and example doctest txt files related incompatibility problem the newer Python version, but the modification is need to work this script future with Python 3.2. If future possible fixing louis Python binding the my prewious letter wrote traceback error message if the Python interpreter is 2.7, we I think safe remove the unicode related prefixes from the test harness files and doctest txt example files. In Python 3.2 this prefixes not need because the strings handle the newest version with unicode format by default. I runned all tests in the check directory after I local modified the test harness files and doctests examples, sending the result file. If the python/louis/__init__.py.in file fixed the wrote unicode decode error related traceback with translation functions, I will be sending already saved modified test documents. After this changes the test system will be work both Python 2.7 and 3.2 version. AttilaFor a description of the software, to download it and links to project pages go to http://www.abilitiessoft.comFor a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com
For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com
