Am 25.01.24 um 20:34 schrieb Miro Hrončok:
$ repoquery -q --repo=rawhide{,-source} --whatrequires flit
...
python-pydyf-0:0.8.0-1.fc40.src
...
weasyprint-0:60.2-1.fc40.src
The packages would probably build fine with flit-core
Indeed, python-pydyf and weasyprint build just fine with flit-c
I patched python-signature-dispatch[1] and python-vecrec[2] so that they
now use flit-core. I’m glad you pointed out that they were using flit.
[1] https://github.com/kalekundert/signature_dispatch/pull/6
[2] https://github.com/kxgames/vecrec/pull/3
On 1/25/24 15:58, Maxwell G wrote:
On Thu J
Am Fr., 26. Jan. 2024 um 09:26 Uhr schrieb Miro Hrončok :
>
> On 26. 01. 24 4:33, Nico Kadel-Garcia wrote:
> > What is the*fascination* with splitting and renaming packages this
> > way?
>
> No idea generally, but in the world of Python packaging,
> the two cases I know (poetry, flit) were motivat
On 26. 01. 24 4:33, Nico Kadel-Garcia wrote:
What is the*fascination* with splitting and renaming packages this
way?
No idea generally, but in the world of Python packaging,
the two cases I know (poetry, flit) were motivated by folks not wanting to pull
in full-blown package and environment m
On Thu Jan 25, 2024 at 20:34 +0100, Miro Hrončok wrote:
> Hello.
Hi Miro,
Thanks for the announcement!
> Now when python-flit-core has been split out of python-flit, I do no longer
> have a use-case for python-flit and hence I have orphaned it.
For context, flit-core is the PEP 517 build backe
Hello.
Now when python-flit-core has been split out of python-flit, I do no longer
have a use-case for python-flit and hence I have orphaned it.
$ repoquery -q --repo=rawhide{,-source} --whatrequires flit
python-perky-0:0.8.2-3.fc39.src
python-pydyf-0:0.8.0-1.fc40.src
python-pyrpm-0:0.14.1-3.f
