cc @dotlambda

Alternatively, we can use pytest_3. But we'll also have to overhaul WebOb's dependencies to prevent multiple versions of pytest in the closure.

Furthermore, would you mind getting rid of buildInputs in favor of nativeBuildInputs and checkInputs?

I don't really see the connection to WebOb, but I can see that WebOb appears to have pytest in its propagatedBuildInputs, which seems wrong.

I don't really see the connection to WebOb

If you use pytest_3 for pygal, you'll get

Found duplicated packages in closure for dependency 'pytest':
  pytest 3.10.1 (/nix/store/b7z68j94dfmfcyl371pqr6ggdsrggwk0-python3.7-pytest-3.10.1/lib/python3.7/site-packages)
  pytest 4.2.1 (/nix/store/jky420fbml8s6b563zzfci3wicni0f5b-python3.7-pytest-4.2.1/lib/python3.7/site-packages)

which is due to WebOb.

Not if I can help it...

@dotlambda ok, I've fixed up WebOb & routes to accommodate the switch of pygal to pytest_3. I had to create a pytestrunner_pytest_3 to go with it though.

There are still downstream rebuilds that don't build, but only those that were already broken.

Noting that there are so many rebuilds, should this be targeted at staging instead of master?

Added a staging rebase of this #60888

No need to open new PR's when rebasing.

It's not so much the rebase that caused it, it's that I was re-pointing it to staging rather than master. If there's a way to re-target a PR, I'd love to know.

top right next to the PR title press edit, a branch selector pops up.

😲 you've changed my life.