-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide Alternative way to run test to avoid Warning #339
Comments
Thanks for reporting this! An option that pops into my mind is to have an environmental value defined that contains the test command, as it is very hard to provide any default command. Setuptools tests are not run by default at the moment either, so guess we just need to deprecate that option at some point |
It can likely be a documentation issue, because tests should prolly be run in an override (i.e. by make), not dh-venv proper. It's not a well-defined target and has too much variation, so put it in the user's hand (with a solid example on how to). |
I kinda agree with this. Here the rules files I've written:
|
Should plan to provide an alternative way to run the test.
python setup.py test
is deprecated.For this reason we dh_virtualenv should provide an alternative way to call the test using nose2 or pytest
The text was updated successfully, but these errors were encountered: