Just had a few minutes to read through the diff...Did you ask shadchin@ about taking maintainer? (To be honest it's a bit rude to propose a diff that just takes maintainer and then ask afterwards..)
On 2018/08/07 22:50, Elias M. Mariani wrote: > Sorry, I forgot about adding devel/py-py to the diff. > > 2018-08-07 18:25 GMT-03:00 Elias M. Mariani <[email protected]>: > > Updating the update > > 2018-07-30 20:20 GMT-03:00 Elias M. Mariani <[email protected]>: > >> Updating the update. > >> All the following changes were tested again, this time against > >> databases/py-sqlalchemy,python3 > >> 1 failed, 7809 passed, 888 skipped > >> > >> The same result as the current, version, the previous update and the > >> current update. > >> (The test uses py-test-xdist, and is very complete) > >> > >> added also > >> devel/py-pluggy > >> Update from 0.6.0 to 0.7.1 > >> https://github.com/pytest-dev/pluggy/blob/master/CHANGELOG.rst > >> Not a single function removed, only deprecated. (the only real > >> consumer is devel/py-test). > >> > >> 2018-07-26 15:13 GMT-03:00 Elias M. Mariani <[email protected]>: > >>> 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 > >> Further update from 3.66.1 to 3.66.14 > >> https://hypothesis.readthedocs.io/en/master/changes.html > >> Mostly performance upgrades and bugfixes. > > devel/py-hypothesis 3.66.14 -> 3.66.30 > > Mostly performance upgrades and bugfixes. > > > >> > >>> devel/py-py > > 1.5.4 > > > >>> devel/py-test > >> Further update from 3.6.3 to 3.6.4 > >> https://github.com/pytest-dev/pytest/blob/master/CHANGELOG.rst > >> No potential problem with the changes. > > devel/py-test 3.6.4 -> 3.7.1 > > Deprecations and bugfixes. > > New depdendencies are at ports@: > > devel/py-pathlib2 and sysutils/py-scandir. > > > >> > >>> devel/py-test-httpbin > > 0.3.0 > > > >>> devel/py-test-localserver > > 0.4.1 > > > >>> devel/py-test-mock > > 1.10.0 > > > >>> devel/py-test-runner > > 4.2 > > > >>> devel/py-test-xdist > >> Further update from 1.22.2 to 1.22.5 > >> https://github.com/pytest-dev/pytest-xdist/blob/master/CHANGELOG.rst > >> No potential problem with the changes. > >> > >>> > >>> 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.
