3 ms·
I have dozens of projects using pytest, generally run under pytest-runner via python3 setup.py -q pytest All now report WARNING: Testing via this com
by jjgreen 5y ago
I have dozens of projects using pytest, generally run under pytest-runner via
python3 setup.py -q pytest
All now report
WARNING: Testing via this command is deprecated and will be removed in a future
version. Users looking for a generic test entry point independent of test runner
are encouraged to use tox.
I asked a question on SO asking for non-tox alternatives, one of the tox devs replied
python setup.py provisions dependencies, however, the way
it does it is considered deprecated and unsupported going
ahead. Instead, users are encouraged to use tox or ensure
their own dependencies. There's no way around that unless
you're willing to fork setuptools, fix the provision issues
and use that.
- omnicognate 5y agoYeah, that's pretty frustrating. The churn in python dependency management has been immense. The incurable optimist in me thinks that there is a set of best practices that are emerging across multiple languages, that there is a "right way to do it" that we're converging on. Poetry seems far closer to that correct approach than anything else I've tried in Python and I hope that means it will have some longevity. The realist in me expects that some time in the next few years there will be another new hotness I'll have to decide whether to migrate all my stuff to.
- maxnoe 5y agoThe alternative is to just run python - m pytest in an environment with all dependencies installed, or pytest In an environment with the package itself installed. Tox automatizes the process of creating such environments. Just out of curiosity, what exactly is your problem with tox?