Chris Jerdonek

> Hi @pwithams! As you say, the default installation of ECOS will be removed in 1.16. @phschiele Did you mean to say 1.6 here? (I know the original commenter said...

Also see issue #98 for comments regarding `nose` and running unit tests.

It occurs to me that we can get around the absence of simplejson (at least for the spec tests) by storing or generating a version of the spec tests in...

With regard to unit tests, my current thinking is to move away from requiring nose. This is primarily because [Distribute's `test`](http://packages.python.org/distribute/python3.html) seems to provide better support for running `2to3` automatically...

Thanks for putting effort into seeing if nose would work. I wouldn't have had a problem with using nose for older versions and Distribute's `test` for newer versions. By the...

For future reference, here is the [simpler, original form](https://github.com/WebKit/webkit/blob/c22921ac1ec573b442016cdeeea1e3708f40f415/WebKitTools/Scripts/webkitpy/test/main.py) of the manual test-collection code I referenced above (just ~100 lines). Also for future reference, `unittest` was new [as of Python...

FYI, I got tox working in the development branch and pushed it. Tests pass for Python 2.4 to 3.2 with one command. Tox's [documentation](http://tox.testrun.org/latest/example/basic.html#a-simple-tox-ini-default-environments) says they support Jython by default.

I'm more convinced not to use nose after seeing [all the open issues](https://github.com/nose-devs/nose/issues?sort=created&direction=desc&state=open) they have. I just ran into [this one](https://github.com/nose-devs/nose/issues/383#issuecomment-5132573) myself.

FYI, I changed the test harness in the development branch so that nose is no longer needed or used. Running tox now tests Python 2.4 through 3.2. Instructions are in...

The code does work with 2.4 and 2.5 (at least as of version 0.5.3), but we can no longer test that with Travis CI. See also issue #137 (which should...