-
Notifications
You must be signed in to change notification settings - Fork 13
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
Move away from setup.py test
and use a better alternative
#75
Comments
Thanks for such a descriptive issue. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with /lifecycle rotten |
/lifecycle frozen |
Is your feature request related to a problem? Please describe.
It would be great if we move away from
setup.py test
command used to trigger unit tests. As an alternative, we could use nox or tox (used in many Python communities).Describe the solution you'd like
Have a solution that seamlessly integrates with Pipfile and does not require maintaining
setup.py
(some components does not need it at all).Let's have a spike which tooling can be used to trigger and maintain the testsuite:
References
The text was updated successfully, but these errors were encountered: