On 10 Oct 2007, at 07:58, Maciek Fijalkowski wrote:
> Jacek Generowicz wrote:
>> What sort of values of --exec should I expect to work/fail?
>>
> should expect python executable. I happily use --exec like
> --exec=python2.4, --exec=pypy-c.
Sure. It works just fine for me with standard Python interpreters,
just not the custom-build.
> Another way to run it is to run py.test
> under custom executable (we use this with pypy-c), like
>
> ~/nsim/pyfem3/pyfem3 py.test interface/nmag
$ pyfem3/pyfem3 py/py/bin/py.test interface/nmag
Traceback (most recent call last):
File "<string>", line 1, in ?
File "py/py/bin/py.test", line 3, in ?
from _findpy import py
ImportError: No module named _findpy
$ echo $PYTHONPATH
/home/jacek/nsim/py
This PYTHONPATH was set by eval `python nsim/py/py/env.py`.
However, if I manually add /home/jacek/nsim/py/py/bin to the
PYTHONPATH, I get more success.
Should env.py be adjusted to include py/py/bin in the PYTHONPATH ?
Now I am left with interesting interactions between the namespace
magic in py.test and the namespace and command line parsing magic in
the custom-built Python, but I'll have to do quite a bit of poking
around to understand exactly what is going on.
Anyway, your suggestion has got me quite a but further.
Thanks.
_______________________________________________
py-dev mailing list
py-dev@codespeak.net
http://codespeak.net/mailman/listinfo/py-dev
