On Sun, 2020-01-12 at 23:24 +0100, Miro HronĨok wrote:
> Please don't mention it as required or even necessarily recommended, as
> it may not be. I intentionally set up my projects such that tox is
> appropriate for upstream CI, not distribution package checking, and
> intend distribution packages to run setup.py test.
The %tox macro runs the tests in current environment.
See
https://github.com/fedora-python/tox-current-env/ for details.
It's not about the environment. It's about what they actually *do*. In
my projects, tox runs linters, coverage checks and unit tests; setup.py
test only runs unit tests. This is a convenient separation because I
find it appropriate to run linters and coverage checks on commits/PRs
for upstream, but there is no point in running them on package builds.
At the same time, `setup.py test` is deprecated.
Sigh. Always nice when people deprecate perfectly well-working
workflows out from underneath you. :/
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net