Re: Running stackless-testsuite
Austin Bingham <[email protected]> Tue, 5 Aug 2014 06:52:06 +0200
| Newsgroups | gmane.comp.python.stackless |
|---|---|
| Message-ID | <CAEZidR02RznB9BVfy0MdFr=GOfyFyWui60Mz_vPBdq7f3VtFNw@mail.gmail.com> |
--===============7543661444792485637== Content-Type: multipart/alternative; boundary=089e0149be9214900504ffda9ee9 --089e0149be9214900504ffda9ee9 Content-Type: text/plain; charset=UTF-8 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 > --089e0149be9214900504ffda9ee9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Ah, ok, I was on the completely wrong track. I had cloned = "stackless-testsuite" from the bitbucket page and was trying to r= un that. Thanks for pointing me in the right direction.<div><br></div><div> 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?</div><div><b= r></div><div>Austin</div></div><div class=3D"gmail_extra"><br><br><div clas= s=3D"gmail_quote"> On Mon, Aug 4, 2014 at 10:53 PM, Richard Tew <span dir=3D"ltr"><<a href= =3D"mailto:[email protected]" target=3D"_blank">[email protected]= om</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg= in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Tests are normally run via Stackless\unittests\runAll.py<br> <br> The tests should work fine in 3.x, as we run them everytime we do a<br> release. =C2=A0The exception is 3.4, which requires updates to get<br> Stackless to work with it still.<br> <br> Cheers,<br> Richard.<br> <div><div class=3D"h5"><br> On 8/5/14, Austin Bingham <<a href=3D"mailto:[email protected]">a= [email protected]</a>> wrote:<br> > Hi all,<br> ><br> > I met Anselm and Christian at EuroPython, and I sort of hinted that I&= #39;d be<br> > happy to set up Travis (or some other similar tool) to run the stackle= ss<br> > tests on each commit. To that end, I've built stackless from sourc= e, but<br> > I'm having mixed luck running the tests. So I've got a few que= stions.<br> ><br> > First, are the tests supposed to work with Python 3? The tests explici= tly<br> > access the __builtin__ module, which is not AFAIK supported in Python = 3. It<br> > doesn't look like there's any attempt to support both version,= but I<br> > thought I'd check.<br> ><br> > Second, what's the proper/expected way of running the tests? Stand= ard<br> > unittest discovery (i.e. python -m unittest discover) seems to work fi= ne,<br> > though nose is picking up more than it probably should (e.g. functions= like<br> > create_type_tests_for_module()). How should I be executing the tests?<= br> ><br> > Thanks for any help on this.<br> ><br> > Austin<br> ><br> <br> </div></div>_______________________________________________<br> Stackless mailing list<br> <a href=3D"mailto:[email protected]">[email protected]</a><br> <a href=3D"http://www.stackless.com/mailman/listinfo/stackless" target=3D"_= blank">http://www.stackless.com/mailman/listinfo/stackless</a><br> </blockquote></div><br></div> --089e0149be9214900504ffda9ee9-- --===============7543661444792485637== 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 --===============7543661444792485637==--