On 20. 12. 21 5:53, Michel Alexandre Salim wrote:
Could you please share the specfile, so I can debug this?
Sure. As it turns out, most of the requirements are indeed superfluous, the
test suite passed just fine with just this:
https://bugzilla.redhat.com/show_bug.cgi?id=2033816
It seems t
*From: *Miro Hrončok
*To: *Fedora Python SIG ; Michel
Alexandre Salim
*Date: *Dec 19, 2021 03:58:57
*Subject: *Re: pyproject-rpm-macros: adding support for Pipfile?
On 17. 12. 21 23:26, Michel Alexandre Salim wrote:
Hi,
Is there interest in
On 17. 12. 21 23:26, Michel Alexandre Salim wrote:
Hi,
Is there interest in supporting parsing Pipfile for build requirements?
Hi. Let me borrow an answer from a similar request somewhere else [1]:
"""Whatever comes out of this, we will probably strive for supporting existing
standards, rath
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
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
