I'm a little hesitant to merge this as-is, because although I'd like to be able to support as many individual use cases as possible, I don't want them to be baked directly into pytest-reqs.
While there aren't any restrictions on what filenames are or are not valid for requirements files, the patterns which are currently supported by pytest-reqs are the same common patterns supported by other automated tools around requirements files (for example, https://requires.io/).
Instead, I think it'd be really great if it was possible to override the patterns being searched via the [pytest] section of a setup.cfg file, for example, with a field such as reqsfilenamepatterns. I've created #7 to address this -- if you're feeling up for it, please feel free to tackle it!
Hey @jhermann! Thanks for your PR.
I'm a little hesitant to merge this as-is, because although I'd like to be able to support as many individual use cases as possible, I don't want them to be baked directly into
pytest-reqs.While there aren't any restrictions on what filenames are or are not valid for requirements files, the patterns which are currently supported by
pytest-reqsare the same common patterns supported by other automated tools around requirements files (for example, https://requires.io/).Instead, I think it'd be really great if it was possible to override the patterns being searched via the
[pytest]section of asetup.cfgfile, for example, with a field such asreqsfilenamepatterns. I've created #7 to address this -- if you're feeling up for it, please feel free to tackle it!