Roundup Tracker - Issues

Message5403

Author jerrykan
Recipients ber, jerrykan, schlatterbeck, techtonik
Date 2016-01-06.00:51:10
Message-id <568C64EE.50603@jerrykan.com>
In-reply-to <1452029721.8.0.813463735518.issue2550894@psf.upfronthosting.co.za>
On 06/01/16 08:35, Bernhard Reiter wrote:
> One problem I have with run_tests.py is that using the pychecker version
> barfs on my. E.g. with hg5009:3766e0ca8e7a :

Just to clarify, this is an issue with the existing run_tests.py script 
and not the new py.test script, and this is one of the reasons you are 
happy to move to a better framework?

On 06/01/16 08:37, Bernhard Reiter wrote:
> So I'm all for moving the a better testing framework.

Once v1.5.1 is released and we can drop python2.5 I'll rebase and 
patches, clean them up a bit a apply them.

> As for the python3. If we manage to scramble resources to do a python3
> "port" I thing we should technically rebuild from scratch to keep the spirit
> and some template compatibility for roundup3.

I've done some experiments on a python3 port, and had some other 
thoughts around some of these things, but I'll leave that discussion for 
another thread. I don't want to distract from a v1.5.1 release, so once 
that is out maybe I'll write up an email to start discussing some of 
these things... which should probably involve the bugs.python.org 
maintainers as well.
History
Date User Action Args
2016-01-06 00:51:11jerrykansetrecipients: + jerrykan, schlatterbeck, ber, techtonik
2016-01-06 00:51:11jerrykanlinkissue2550894 messages
2016-01-06 00:51:10jerrykancreate