Running stackless-testsuite
Austin Bingham <[email protected]> Mon, 4 Aug 2014 20:57:06 +0200
| Newsgroups | gmane.comp.python.stackless |
|---|---|
| Message-ID | <CAEZidR1oE=3Dzgq4Mv84m4gQvD+ZRr3vcJwy3+Uu54=Mnw1p1g@mail.gmail.com> |
--===============7922241704498985508== Content-Type: multipart/alternative; boundary=089e0160bc682ddfaa04ffd24e0e --089e0160bc682ddfaa04ffd24e0e Content-Type: text/plain; charset=UTF-8 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 --089e0160bc682ddfaa04ffd24e0e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hi all,<div><br></div><div>I met Anselm and Christian at E= uroPython, 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 r= unning the tests. So I've got a few questions.</div> <div><br></div><div>First, are the tests supposed to work with Python 3? Th= e tests explicitly access the __builtin__ module, which is not AFAIK suppor= ted in Python 3. It doesn't look like there's any attempt to suppor= t both version, but I thought I'd check.</div> <div><br></div><div>Second, what's the proper/expected way of running t= he tests? Standard unittest discovery (i.e. python -m unittest discover) se= ems 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 executi= ng the tests?</div> <div><br></div><div>Thanks for any help on this.</div><div><br></div><div>A= ustin</div> <div><br></div><div><br></div></div> --089e0160bc682ddfaa04ffd24e0e-- --===============7922241704498985508== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless --===============7922241704498985508==--