myhdl-list

[myhdl-list] cpython, pypy, and py.test

[Christopher F. <chr...@gm...>]

Does anyone have a good method to use either, cpython or pypy, with 
py.test?

When running test suites built around py.test it would be nice to 
indicate which interpreter to use.

Couple issues I ran into:

  1.  Installing py.test requires easy_install (or pip,
      no source install available?) and I did not see how
      to indicate which python installation to use with easy_install?
      (So that the py.test framework is installed for both versions)

  2.  Would you simply modify the py.test top script to indicate which
      python interpreter to use?

Regards,
Chris

Re: [myhdl-list] cpython, pypy, and py.test

[Martín G. <ga...@gm...>]

On Sun, Jun 26, 2011 at 3:52 PM, Christopher Felton
<chr...@gm...> wrote:
> Does anyone have a good method to use either, cpython or pypy, with
> py.test?
>
> When running test suites built around py.test it would be nice to
> indicate which interpreter to use.
>
> Couple issues I ran into:
>
>  1.  Installing py.test requires easy_install (or pip,
>      no source install available?) and I did not see how
>      to indicate which python installation to use with easy_install?
>      (So that the py.test framework is installed for both versions)
>
>  2.  Would you simply modify the py.test top script to indicate which
>      python interpreter to use?
>
> Regards,
> Chris

I told few days ago [0], this is what Tox [1] is for

[1] http://tox.readthedocs.org

[0] http://article.gmane.org/gmane.comp.python.myhdl/1997/match=tox

Re: [myhdl-list] cpython, pypy, and py.test

[Christopher F. <chr...@gm...>]

On 6/26/11 4:26 PM, Martín Gaitán wrote:
> On Sun, Jun 26, 2011 at 3:52 PM, Christopher Felton
> <chr...@gm...>  wrote:
>> Does anyone have a good method to use either, cpython or pypy, with
>> py.test?
>>
>> When running test suites built around py.test it would be nice to
>> indicate which interpreter to use.
>>
>> Couple issues I ran into:
>>
>>   1.  Installing py.test requires easy_install (or pip,
>>       no source install available?) and I did not see how
>>       to indicate which python installation to use with easy_install?
>>       (So that the py.test framework is installed for both versions)
>>
>>   2.  Would you simply modify the py.test top script to indicate which
>>       python interpreter to use?
>>
>> Regards,
>> Chris
>
> I told few days ago [0], this is what Tox [1] is for
>
> [1] http://tox.readthedocs.org
>
> [0] http://article.gmane.org/gmane.comp.python.myhdl/1997/match=tox
>

Thanks, I guess I missed tox usage or forget.  D'oh, thanks for the 
reminder.

Chris

Re: [myhdl-list] cpython, pypy, and py.test

[Dan W. <eti...@gm...>]

On Sun, Jun 26, 2011 at 1:52 PM, Christopher Felton
<chr...@gm...> wrote:
> Does anyone have a good method to use either, cpython or pypy, with
> py.test?


Jan's speed post came about just as I was testing some HDL for an
upcoming mixed-signal ASIC, here's the hack-way I've done it:
(requires the extra pytest-xdist plugin)

py.test --dist=load --tx 4*popen//python=pypy
and half the processes when using cosimulation

It's been a killer combination for long-running tests, especially when
using Rackspace instances to keep my main machine free while they run.
 For some reason, running as a module under pypy fails if there are
extra cmd line arguments related to xdist, hence the above
work-around:

"python -m pytest foo.py" and
"python -m pytest -n4 foo.py" and
"pypy -m pytest -v foo.py" work properly, but any options fail with e.g.:
"pypy -m pytest -n4 foo.py"

tox would be better for more formal multi-platform release stuff, though.

HTH,

Dan


-- 
SDG
www.whiteaudio.com

Re: [myhdl-list] cpython, pypy, and py.test

[Christopher F. <chr...@gm...>]

Thanks to all for the suggestions, things learned thus far:

  1. Installed tox and created the example tox.ini file.  It complained 
about a missing setup.py file in the directory that I was trying to run 
the tests.  Not sure what this error is, will need to investigate later.

  2.  My case, using pytest as a module (-m) appeared straight-forward. 
  But I couldn't resolve how to install pytest for different installed 
interpreters.  This might be something very basic that I am overlooking.

Thanks again for the comments.
Chris