Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #14200 > unrolled thread

pdm-pep517: Shall we package it now?

Back to article view | Back to linux.debian.maint.python

Contents

  pdm-pep517: Shall we package it now? Boyuan Yang <byang@debian.org> - 2022-06-28 15:30 +0200
    Re: pdm-pep517: Shall we package it now? Stefano Rivera <stefanor@debian.org> - 2022-06-28 15:40 +0200
      Re: pdm-pep517: Shall we package it now? Boyuan Yang <byang@debian.org> - 2022-06-29 17:00 +0200
        Re: pdm-pep517: Shall we package it now? Julian Gilbey <julian@d-and-j.net> - 2022-06-30 08:40 +0200
    Re: pdm-pep517: Shall we package it now? Louis-Philippe Véronneau <pollo@debian.org> - 2022-06-28 17:20 +0200
      Re: pdm-pep517: Shall we package it now? Boyuan Yang <byang@debian.org> - 2022-07-07 21:40 +0200
        Re: pdm-pep517: Shall we package it now? Louis-Philippe Véronneau <pollo@debian.org> - 2022-07-08 08:00 +0200
        Re: pdm-pep517: Shall we package it now? Julian Gilbey <julian@d-and-j.net> - 2022-07-08 09:40 +0200
    Packaging of pdm (Was: pdm-pep517: Shall we package it now?) Boyuan Yang <byang@debian.org> - 2022-07-03 00:50 +0200
      Re: Packaging of pdm (Was: pdm-pep517: Shall we package it now?) Louis-Philippe Véronneau <pollo@debian.org> - 2022-07-08 09:20 +0200

#14200 — pdm-pep517: Shall we package it now?

[Multipart message — attachments visible in raw view] — view raw

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!

Regards,
Boyuan Yang


[1] https://codesearch.debian.net/search?q=pdm.pep517
[2] https://github.com/pdm-project/pdm-pep517

[toc] | [next] | [standalone]

#14201

Hi Boyuan (2022.06.28_13:24:49_+0000)
> 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.

Yes, probably time to package it.

Bootstrapping shouldn't be problematic, PEP517 includes support for
bootstrapping (backend-path = ["."]), so backends can build themselves
from their own source trees.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

[toc] | [prev] | [next] | [standalone]

#14205

[Multipart message — attachments visible in raw view] — view raw

Hi,

在 2022-06-28星期二的 13:32 +0000，Stefano Rivera写道：
> Hi Boyuan (2022.06.28_13:24:49_+0000)
> > 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.
> 
> Yes, probably time to package it.
> 
> Bootstrapping shouldn't be problematic, PEP517 includes support for
> bootstrapping (backend-path = ["."]), so backends can build themselves
> from their own source trees.

Thanks. I have uploaded an initial version to the NEW queue. The packaging
work is at https://salsa.debian.org/python-team/packages/pdm-pep517/ .

It is worth noting that I took the very aggressive way in stripping every
vendored libraries, see
https://salsa.debian.org/python-team/packages/pdm-pep517/-/tree/master/debian/patches
. This may not be ideal since the patch will need human intervention for every
new upstream release, but anyway let's have a working version in Sid first.
Meanwhile, any review or other types of help would be appreciated.

Thanks,
Boyuan Yang

[toc] | [prev] | [next] | [standalone]

#14208

On Wed, Jun 29, 2022 at 10:58:48AM -0400, Boyuan Yang wrote:
> Hi,
> [...]
> Thanks. I have uploaded an initial version to the NEW queue. The packaging
> work is at https://salsa.debian.org/python-team/packages/pdm-pep517/ .
> 
> It is worth noting that I took the very aggressive way in stripping every
> vendored libraries, see
> https://salsa.debian.org/python-team/packages/pdm-pep517/-/tree/master/debian/patches
> . This may not be ideal since the patch will need human intervention for every
> new upstream release, but anyway let's have a working version in Sid first.
> Meanwhile, any review or other types of help would be appreciated.

Hi Boyuan,

I've just taken a look; the exclusions and patching look fine to me.
Yes, there will need to be some human intervention, but there always
should be for new upstream versions.  It may well be that all that is
needed is to refresh the patch and run:

quilt push -a
rgrep _vendor pdm

(or the equivalent gbp pq push or something like that) to check that
nothing has changed.

One small change to the patch:

* In pdm/pep517/utils.py and pdm/pep517/wheel.py, there is no need to
  insert an "import packaging"

Best wishes,

   Julian

[toc] | [prev] | [next] | [standalone]

#14202

On 2022-06-28 09 h 24, Boyuan Yang wrote:
> 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!
> 
> Regards,
> Boyuan Yang
> 
> 
> [1] https://codesearch.debian.net/search?q=pdm.pep517
> [2] https://github.com/pdm-project/pdm-pep517

Once packaged, please ping me so I can update the
"missing-prerequisite-for-pyproject-backend" Lintian tag accordingly and
let people know they can migrate to it.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   pollo@debian.org / veronneau.org
  ⠈⠳⣄

[toc] | [prev] | [next] | [standalone]

#14224

[Multipart message — attachments visible in raw view] — view raw

Hi,

在 2022-06-28星期二的 11:19 -0400，Louis-Philippe Véronneau写道：
> On 2022-06-28 09 h 24, Boyuan Yang wrote:
> > 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!
> > 
> > Regards,
> > Boyuan Yang
> > 
> > 
> > [1] https://codesearch.debian.net/search?q=pdm.pep517
> > [2] https://github.com/pdm-project/pdm-pep517
> 
> Once packaged, please ping me so I can update the
> "missing-prerequisite-for-pyproject-backend" Lintian tag accordingly and
> let people know they can migrate to it.

This is now accepted at https://tracker.debian.org/pkg/pdm-pep517 .

Cheers,
Boyuan Yang

[toc] | [prev] | [next] | [standalone]

#14226

On 2022-07-07 15 h 36, Boyuan Yang wrote:
> Hi,
> 
> 在 2022-06-28星期二的 11:19 -0400，Louis-Philippe Véronneau写道：
>> On 2022-06-28 09 h 24, Boyuan Yang wrote:
>>> 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!
>>>
>>> Regards,
>>> Boyuan Yang
>>>
>>>
>>> [1] https://codesearch.debian.net/search?q=pdm.pep517
>>> [2] https://github.com/pdm-project/pdm-pep517
>>
>> Once packaged, please ping me so I can update the
>> "missing-prerequisite-for-pyproject-backend" Lintian tag accordingly and
>> let people know they can migrate to it.
> 
> This is now accepted at https://tracker.debian.org/pkg/pdm-pep517 .

Thanks for the work on this.

Here's the lintian MR for reference:

https://salsa.debian.org/lintian/lintian/-/merge_requests/400

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   pollo@debian.org / veronneau.org
  ⠈⠳⣄

[toc] | [prev] | [next] | [standalone]

#14228

On Thu, Jul 07, 2022 at 03:36:30PM -0400, Boyuan Yang wrote:
> Hi,
> 
> 在 2022-06-28星期二的 11:19 -0400，Louis-Philippe Véronneau写道：
> > On 2022-06-28 09 h 24, Boyuan Yang wrote:
> > > 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!
> > > 
> > > Regards,
> > > Boyuan Yang
> > > 
> > > 
> > > [1] https://codesearch.debian.net/search?q=pdm.pep517
> > > [2] https://github.com/pdm-project/pdm-pep517
> > 
> > Once packaged, please ping me so I can update the
> > "missing-prerequisite-for-pyproject-backend" Lintian tag accordingly and
> > let people know they can migrate to it.
> 
> This is now accepted at https://tracker.debian.org/pkg/pdm-pep517 .
> 
> Cheers,
> Boyuan Yang

Brilliant!  Thanks for this!  (I think you'll need to do a source-only
upload now to allow migration to testing, unless the procedures have
changed recently.)

Best wishes,

   Julian

[toc] | [prev] | [next] | [standalone]

#14210 — Packaging of pdm (Was: pdm-pep517: Shall we package it now?)

[Multipart message — attachments visible in raw view] — view raw

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

Thanks,
Boyuan Yang

[toc] | [prev] | [next] | [standalone]

#14227 — Re: Packaging of pdm (Was: pdm-pep517: Shall we package it now?)

On 2022-07-03 00 h 49, Boyuan Yang wrote:
> 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

Nice!

As I'm sure people will confuse "python3-pdm" (the cli tool) and
"python3-pdm-pep517" (the tool used to build packages), I've created a
Lintian tag:

https://salsa.debian.org/lintian/lintian/-/merge_requests/401

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   pollo@debian.org / veronneau.org
  ⠈⠳⣄

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web