Hi all,
I have encountered more and more packages that uses pdm-pep517 as build backend. Looking at [1], existing packages in Debian added patches to manually switch to other backends, such as Poetry.
I am wondering if it's time to package pdm-pep517 itself [2], or is there
any blocking for it. I am aware that some sort of bootstrapping might be needed since pdm-pep517 seems to build-depends on itself. Besides that,
what
about packaging of pdm? Please correct me if needed: my mind and my
packaging work is still stuck in the old times of setup.py, and I just started to look into the new ecosystem of pep517. Thanks!
Hi all,
在 2022-06-28星期二的 09:24 -0400,Boyuan Yang写道:
Hi all,
I have encountered more and more packages that uses pdm-pep517 as build
backend. Looking at [1], existing packages in Debian added patches to
manually switch to other backends, such as Poetry.
I am wondering if it's time to package pdm-pep517 itself [2], or is there
any blocking for it. I am aware that some sort of bootstrapping might be
needed since pdm-pep517 seems to build-depends on itself. Besides that,
what
about packaging of pdm? Please correct me if needed: my mind and my
packaging work is still stuck in the old times of setup.py, and I just
started to look into the new ecosystem of pep517. Thanks!
As an update, I also pushed pdm package [3] as well as several of its build- dependencies into the NEW queue.
[3] http://salsa.debian.org/python-team/packages/pdm
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 435 |
Nodes: | 16 (2 / 14) |
Uptime: | 138:07:58 |
Calls: | 9,117 |
Files: | 13,422 |
Messages: | 6,032,813 |