holger at merlinux.eu
Thu Apr 9 11:57:00 PDT 2009
On Thu, Apr 09, 2009 at 13:36 -0500, Kumar McMillan wrote:
> On Thu, Apr 9, 2009 at 1:27 PM, Doug Philips <dgou at mac.com> wrote:
> > IIRC, at PyCon 2009, the py.test folks demo'd that very thing. IIRC2, you didn't need to have py.test already installed on the remote system, but I'm not sure.
> At the moment I believe you need the whole pypy package to use it?
huh? beware! :)
With "easy_install py" you'll get some 10 KLocs of actual code
(it comes with tests and all - i am currently working hard on
streamlining and downstripping the core code, btw)
> Holger can jump in and clarify but the piece at work was pyexecnet (?)
> and as I recall this will be pulled out of pypy soon into a standalone
> package for nose and anything else to use.
no PyPy needed at all. See here for more info on distribution topics:
> > Given the cross-polination between nose and py.test I would be suprised if this ability weren't already on the radar of the nose developers. Ideally it could be abstracted out for other testing frameworks to use too.
> > -Doug
> > _______________________________________________
> > testing-in-python mailing list
> > testing-in-python at lists.idyll.org
> > http://lists.idyll.org/listinfo/testing-in-python
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
Metaprogramming, Python, Testing: http://tetamap.wordpress.com
Python, PyPy, pytest contracting: http://merlinux.eu
More information about the testing-in-python