Ah, ok, I was on the completely wrong track. I had cloned "stackless-testsuite" from the bitbucket page and was trying to run that. Thanks for pointing me in the right direction.
On that topic, though, what is stackless-testsuite for? It looks to be very new, so is it perhaps the future home of the stackless tests? Austin On Mon, Aug 4, 2014 at 10:53 PM, Richard Tew <richard.m....@gmail.com> wrote: > Tests are normally run via Stackless\unittests\runAll.py > > The tests should work fine in 3.x, as we run them everytime we do a > release. The exception is 3.4, which requires updates to get > Stackless to work with it still. > > Cheers, > Richard. > > On 8/5/14, Austin Bingham <austin.bing...@gmail.com> wrote: > > Hi all, > > > > I met Anselm and Christian at EuroPython, and I sort of hinted that I'd > be > > happy to set up Travis (or some other similar tool) to run the stackless > > tests on each commit. To that end, I've built stackless from source, but > > I'm having mixed luck running the tests. So I've got a few questions. > > > > First, are the tests supposed to work with Python 3? The tests explicitly > > access the __builtin__ module, which is not AFAIK supported in Python 3. > It > > doesn't look like there's any attempt to support both version, but I > > thought I'd check. > > > > Second, what's the proper/expected way of running the tests? Standard > > unittest discovery (i.e. python -m unittest discover) seems to work fine, > > though nose is picking up more than it probably should (e.g. functions > like > > create_type_tests_for_module()). How should I be executing the tests? > > > > Thanks for any help on this. > > > > Austin > > > > _______________________________________________ > Stackless mailing list > Stackless@stackless.com > http://www.stackless.com/mailman/listinfo/stackless >
_______________________________________________ Stackless mailing list Stackless@stackless.com http://www.stackless.com/mailman/listinfo/stackless
