[Bug 227862] devel/py-tox: update to 3.0.0

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227862

--- Comment #5 from Kubilay Kocak <koobs at FreeBSD.org> ---
(In reply to Kai from comment #4)

testport -i is different to -I so may produce different results, but the test
target for ports already installs build/run depends and has them installed at
that point, so theoretically the behaviour shouldn't be different.

The issue with tox is that is creates a virtualenv that doesn't inherit from
system site-packages by default, so those environments cant see the modules
that were installed by ports (poudriere), and so tox tries to install them.

I tried to make tox allow (enable) --sitepackages, but saw a different set of
test failures in that case, which is why I switched it back to using bare
pytest (which is what tox calls anyway).

Warnings, all else being equal, either imply dependencies in setup.py
(*_requires) are incorrect/incomplete and need to be fixed, but in this case i
dont believe that's the cause.

My current thought is that maybe since pluggy (etc) are *run time*
dependencies, but building docs (with sphinx) is a *build* time activity,
that's whats producing the warnings. That would imply pluggy (if it is indeed
required to build docs), should be a setup_requires, at least conditionally in
the setup.py build docs target. However, I'm guessing its not actually
required, but instead the warnings are an artifact of something else.

-- 
You are receiving this mail because:
You are on the CC list for the bug.