[pytest-dev] maintenance of pytest-html

[Florian Bruhin]

On Wed, Jul 29, 2020 at 02:59:24PM +0100, Thomas Grainger wrote:
> > Why? Something like a tox environment running against the latest pytest
> > prerelease (or pytest master even) plus a scheduled build job should totally
> > suffice, no?
> 
> -1 on depending on unpined deps in CI this causes the default branch
> to fail and blocks all contributions until it is resolved
> Creating a pr (in pyup.io) gives one point of discussion if a release
> fails and does not block any other prs

Agreed! Just because the environment exists, it doesn't mean it has to run for
PRs. Similarly, it doesn't make sense to run e.g. linters periodically.

In other words, run environments with pinned versions for PRs/branches, run an
environment with unpinned (and prerelease/VCS) dependencies periodically.

Florian

-- 
me at the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
       https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
       GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
             I love long mails! | https://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20200729/fc6ce3cb/attachment.sig>