You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We do pip install --pre ... in tox.ini. This means our testing tools like coverage, black, isort etc (and I suppose their dependencies) may be pre-releases.
This has been the case since 2015 but it sounds like a bad idea. Should we drop the --pre?
The text was updated successfully, but these errors were encountered:
Keep using newest versions of build tools, but don't use pre-releases:
* less downloading (with chances of failures) happens in the CI because
versions change less often
* tools are less likely to break the build (or at least it happens less
often)
This change should not affect the software under test as we install
pinned versions of those.
Note that this also doesn't affect black: tox still ends up with a
pre-release version of black because that project has never made an
actual release.
Fixestheupdateframework#1350
Signed-off-by: Jussi Kukkonen <jkukkonen@vmware.com>
We do
pip install --pre ...
in tox.ini. This means our testing tools like coverage, black, isort etc (and I suppose their dependencies) may be pre-releases.This has been the case since 2015 but it sounds like a bad idea. Should we drop the
--pre
?The text was updated successfully, but these errors were encountered: