Easy mistake to make. See the following link for information about the stackless-testsuite project. It slightly predates your joining the list.
http://www.stackless.com/pipermail/stackless/2014-July/006393.html Looking forward to seeing what you come up with, as it sounds like something we've long needed. There were vague ideas that CCP might be able to provide something similar at one point, but CCP no longer employs any Stackless Python developers and is I assume after 13 years of Stackless support is moving on. Cheers, Richard. On 8/5/14, Austin Bingham <[email protected]> wrote: > 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 <[email protected]> > 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 <[email protected]> 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 >> [email protected] >> http://www.stackless.com/mailman/listinfo/stackless >> > _______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless
