Moving the thread just to change the title to something more descriptive. Hi, I have the following list of ports, all share interdependencies between them, thats why I think that the best would be to commit the hole thing together. I'm talking about py-test. I have the diff ready to update: devel/py-hypothesis devel/py-py devel/py-test devel/py-test-httpbin devel/py-test-localserver devel/py-test-mock devel/py-test-runner devel/py-test-xdist
And a tarball with: devel/py-test-forked (new dependency of devel/py-test-xdist). To check for the possibility of this updates affecting other ports I checked every port using the current versions vs the updated versions, the results are attached. The format is: FULLPKGPATH Result using current version Result using new version (if differences exist, none if equals) The only ones giving a different result are: www/py-httpie 4 failed, 223 passed, 4 skipped, 13 warnings Error: fixture is being applied more than once to the same function devel/py-doit 2 failed, 731 passed, 21 skipped Error: fixture is being applied more than once to the same function According to the pytest changelog: "Now when @pytest.fixture is applied more than once to the same function a ValueError is raised. This buggy behavior would cause surprising problems and if was working for a test suite it was mostly by accident." https://docs.pytest.org/en/latest/changelog.html#pytest-3-6-0-2018-05-23 So I think that with this we can rest assure that the updates work fine. With that I propose to update the versions with the unified diff that I attached as well, and the new dependency on py-test-xdist: py-test-forked (also attached...). Doing the change at once seems to me reasonable given the interdependency and also the way in witch I made the tests. Cheers. Elias.
py-test-forked.tar.gz
Description: GNU Zip compressed data
tests.results
Description: Binary data
udiff.diff
Description: Binary data
