Hi.I'm not sure about it but if we'd want to support something like this, I'd use micropipenv [0] to transfer Pipfile[.lock] or poetry.lock into requirements.txt which we can then use with the existing logic.
Lumír [0] https://github.com/thoth-station/micropipenv On 12/17/21 23:26, Michel Alexandre Salim wrote:
Hi, Is there interest in supporting parsing Pipfile for build requirements? e.g. MonkeyType uses it to list its dependencies: https://github.com/instagram/MonkeyType For now I can just add requirements by hand, `%pyproject_buildrequires -r` does not error out but also does not generate anything. Thanks, _______________________________________________ python-devel mailing list --python-devel@lists.fedoraproject.org To unsubscribe send an email topython-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/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure
_______________________________________________ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure