Hi Holger and list members,
I have been using py.test for some time after switching from nose and
quite happy with it.
However, when migrating from 1.3.1 to 2.0.2 I hit a couple of snags,
which makes me hesitate.
Perhaps you can help me.
1. Just to clear the point. I understand from another post that
option_xxxx variables
in conftest.py are gone and recommended replacement is to use
pytest_cmdline_preparse().
Is that so?
2. The new behavior is that even if you run py.test --help, the
pytest_configure() is still run.
In my case pytest_configure() does quite a bit of heavy lifting and
raises exceptions at
wrong parameters. The result is that if the parameter is wrong I
cannot use help to find
out what is the right parameter. Of course, the workaround could be:
def pytest_configure(config):
if config.getvalue('help'):
return
...
but it seems ugly. Am I in a wrong hook?
3. In my pytest_configure() there are numerous conditions when it can
fail. For this
conditions I have exceptions with specially crafted messages, intended
for different
people. Now they are gone, replaced by a long and scary listing with every line
prepended with INTERNALERROR. What is internal about it? Can I continue managing
my configuration errors?
Thanks,
Vyacheslav
_______________________________________________
py-dev mailing list
py-dev@codespeak.net
http://codespeak.net/mailman/listinfo/py-dev
