Re: [pytest-dev] Transfer of pyfakefs to pytest-dev - second try

Thank you Sorin and Bruno! The documentation (https://docs.pytest.org/en/7.1.x/contributing.html#submitting-plugins-to-pytest-dev) states that the repository can be transferred "if no contributor strongly objects and two agree". We got two votes, so I will wait a bit more for objections, and

[pytest-dev] On ensuring sustainable maintenance of pytest-dev projects

Hi everyone, Please read with the caveat that this stems from a gut feeling that's not yet quantitative verified. As pytest-dev is growing, so is the number of projects that suffer bus-factor and/or non-maintenance. I believe a more active approach to ensuring maintenance /maintainer influx i

[pytest-dev] assessing hatch/hatching for python package management

Hi everyone, in https://github.com/pytest-dev/pluggy/pull/362 i prepared to move pluggy to hatch. I hope to eventually move most if not all of pytest-dev over to it. Hatch is a new and modern tool for python package creation. it follows the relevant peps, and has a superset of tox features a

[pytest-dev] introducing collection boundaries to support expanding fixtures to non-python and testsuites as python packages

Hi everyone, i would like to break open a number of limitations we have in the collection system. 1. parametrize is tied painfully into Python Items I want to finish my experiment for function definitions and generalize them This would mean that instead of multiple python collectors invoking