On Thu, 10 Nov 2022, Ben Beasley wrote:
In one week (2022-11-17), or slightly later, I will update python-pytest-bdd from version 5.0.0 to version 6.1.1[1] in Rawhide. This will bring significant API-breaking changes[2] from 5.x. The sole dependent package, jrnl, does not support version 6.x yet[3], and the changes required are nontrivial. I will therefore maintain a python-pytest-bdd5 compat package until jrnl is ready for 6.x. Because the changes required to support parallel-installability would be too complex and invasive to be practical, the compat package will explicitly conflict with python-pytest-bdd. The impact of this conflict will be minimal since jrnl uses pytest-bdd only as a BuildRequires for running its tests, and the compat package will not typically be installed on user systems.[1] https://src.fedoraproject.org/rpms/python-pytest-bdd/pull-request/2 [2] https://github.com/pytest-dev/pytest-bdd/releases/tag/6.0.0 [3] https://github.com/jrnl-org/jrnl/issues/1534
It begs the question: if the only user of python-pytest-bdd doesn't support the new version, then why update it? Why not just wait until jrnl supports it? Seems like it would be less work than adding a compat package.
Scott
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
