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

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

Updating python-build/getting rid of pep517

Started byScott Kitterman <debian@kitterman.com>
First post2023-08-01 22:00 +0200
Last post2023-08-02 15:50 +0200
Articles 9 — 3 participants

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

Contents

  Updating python-build/getting rid of pep517 Scott Kitterman <debian@kitterman.com> - 2023-08-01 22:00 +0200
    Re: Updating python-build/getting rid of pep517 Scott Talbert <swt@techie.net> - 2023-08-02 00:40 +0200
      Re: Updating python-build/getting rid of pep517 Scott Kitterman <debian@kitterman.com> - 2023-08-02 01:10 +0200
        Re: Updating python-build/getting rid of pep517 Scott Talbert <swt@techie.net> - 2023-08-02 01:40 +0200
          Re: Updating python-build/getting rid of pep517 Scott Kitterman <debian@kitterman.com> - 2023-08-02 06:20 +0200
            Re: Updating python-build/getting rid of pep517 Éric Araujo <merwok@netwok.org> - 2023-08-02 15:30 +0200
              Re: Updating python-build/getting rid of pep517 Scott Kitterman <debian@kitterman.com> - 2023-08-02 16:00 +0200
            Re: Updating python-build/getting rid of pep517 Scott Talbert <swt@techie.net> - 2023-08-02 15:40 +0200
              Re: Updating python-build/getting rid of pep517 Scott Kitterman <debian@kitterman.com> - 2023-08-02 15:50 +0200

#15087 — Updating python-build/getting rid of pep517

FromScott Kitterman <debian@kitterman.com>
Date2023-08-01 22:00 +0200
SubjectUpdating python-build/getting rid of pep517
Message-ID<GY3Hb-4mhY-3@gated-at.bofh.it>

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

The pep517 package has been renamed pyproject-hooks upstream:

https://github.com/pypa/pyproject-hooks

It looks like we need this to update python-build to the latest version (which 
we should definitely do sooner rather than later).

Is anyone up  for packaging this?

Once it's in the archive we ought to make sure all current users of pep517 are 
switched so we can remove it this cycle.

Scott K

[toc] | [next] | [standalone]

#15088

FromScott Talbert <swt@techie.net>
Date2023-08-02 00:40 +0200
Message-ID<GY6c1-4oYZ-11@gated-at.bofh.it>
In reply to#15087
On Tue, 1 Aug 2023, Scott Kitterman wrote:

> The pep517 package has been renamed pyproject-hooks upstream:
>
> https://github.com/pypa/pyproject-hooks
>
> It looks like we need this to update python-build to the latest version (which
> we should definitely do sooner rather than later).
>
> Is anyone up  for packaging this?
>
> Once it's in the archive we ought to make sure all current users of pep517 are
> switched so we can remove it this cycle.

I'll go ahead and start packaging it.

Regards,
Scott Talbert

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

#15089

FromScott Kitterman <debian@kitterman.com>
Date2023-08-02 01:10 +0200
Message-ID<GY6F3-4pPP-1@gated-at.bofh.it>
In reply to#15088

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

On Tuesday, August 1, 2023 6:22:26 PM EDT Scott Talbert wrote:
> On Tue, 1 Aug 2023, Scott Kitterman wrote:
> > The pep517 package has been renamed pyproject-hooks upstream:
> > 
> > https://github.com/pypa/pyproject-hooks
> > 
> > It looks like we need this to update python-build to the latest version
> > (which we should definitely do sooner rather than later).
> > 
> > Is anyone up  for packaging this?
> > 
> > Once it's in the archive we ought to make sure all current users of pep517
> > are switched so we can remove it this cycle.
> 
> I'll go ahead and start packaging it.

Excellent.  PEP517 has a few users that will need to be ported/updated:

Reverse-Depends
===============
* python3-build (update to new version, needs pyproject-hooks)
* python3-pdm (update to new version, needs pyproject-hooks)
[pdm-pep517 can probably go away too]

Reverse-Testsuite-Triggers
==========================
* poetry-core (update to new version, does use either anymore)

Reverse-Build-Depends
=====================
* check-manifest (does not list pep517 as a requirement, just drop?)
* pdm
* poetry-core
* py7zr (update to new version, does use either anymore)
* python-build
* sniffles (update to new version, does use either anymore)

Looks like no porting will be needed, just updating.  With the exception of 
sniffles, these are all maintained in the Debian Python Team, so this ought to 
be eminently doable.

Scott K

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

#15090

FromScott Talbert <swt@techie.net>
Date2023-08-02 01:40 +0200
Message-ID<GY785-4qlY-5@gated-at.bofh.it>
In reply to#15089
On Tue, 1 Aug 2023, Scott Kitterman wrote:

>> On Tue, 1 Aug 2023, Scott Kitterman wrote:
>>> The pep517 package has been renamed pyproject-hooks upstream:
>>>
>>> https://github.com/pypa/pyproject-hooks
>>>
>>> It looks like we need this to update python-build to the latest version
>>> (which we should definitely do sooner rather than later).
>>>
>>> Is anyone up  for packaging this?
>>>
>>> Once it's in the archive we ought to make sure all current users of pep517
>>> are switched so we can remove it this cycle.
>>
>> I'll go ahead and start packaging it.
>
> Excellent.  PEP517 has a few users that will need to be ported/updated:

Initial packaging done, on its way into NEW.

Scott T.

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

#15091

FromScott Kitterman <debian@kitterman.com>
Date2023-08-02 06:20 +0200
Message-ID<GYbv3-4uze-1@gated-at.bofh.it>
In reply to#15090

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

On Tuesday, August 1, 2023 7:36:38 PM EDT Scott Talbert wrote:
> On Tue, 1 Aug 2023, Scott Kitterman wrote:
> >> On Tue, 1 Aug 2023, Scott Kitterman wrote:
> >>> The pep517 package has been renamed pyproject-hooks upstream:
> >>> 
> >>> https://github.com/pypa/pyproject-hooks
> >>> 
> >>> It looks like we need this to update python-build to the latest version
> >>> (which we should definitely do sooner rather than later).
> >>> 
> >>> Is anyone up  for packaging this?
> >>> 
> >>> Once it's in the archive we ought to make sure all current users of
> >>> pep517
> >>> are switched so we can remove it this cycle.
> >> 
> >> I'll go ahead and start packaging it.
> > 
> > Excellent.  PEP517 has a few users that will need to be ported/updated:
> Initial packaging done, on its way into NEW.
> 
And it's in Unstable now, so it would be good if people could start updating 
the relevant team packages.  I filed #1042869 for the one package not in DPT.

* python-build (update to new version, needs pyproject-hooks)
* pdm (update to new version, needs pyproject-hooks)
  [pdm-pep517 can probably go away too]
* poetry-core (update to new version, does use either anymore)
* check-manifest (does not list pep517 as a requirement, just drop?)
* py7zr (update to new version, does use either anymore)

If anyone doesn't have time to update a package for which they are the 
uploader/maintainer, please reply to the list so someone else can do a team 
upload.

Scott K

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

#15092

FromÉric Araujo <merwok@netwok.org>
Date2023-08-02 15:30 +0200
Message-ID<GYk5k-4Bbp-5@gated-at.bofh.it>
In reply to#15091
Le 02/08/2023 à 00:09, Scott Kitterman a écrit :
> * pdm (update to new version, needs pyproject-hooks)
>    [pdm-pep517 can probably go away too]

pdm-pep517 was renamed to pdm-backend, which will still be needed by 
Python packages who want to use it as a build backend.  (It does not 
depend on pyproject-hooks.)

   Cheers

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

#15095

FromScott Kitterman <debian@kitterman.com>
Date2023-08-02 16:00 +0200
Message-ID<GYkyl-4BpW-7@gated-at.bofh.it>
In reply to#15092

On August 2, 2023 1:23:15 PM UTC, "Éric Araujo" <merwok@netwok.org> wrote:
>Le 02/08/2023 à 00:09, Scott Kitterman a écrit :
>> * pdm (update to new version, needs pyproject-hooks)
>>    [pdm-pep517 can probably go away too]
>
>pdm-pep517 was renamed to pdm-backend, which will still be needed by Python packages who want to use it as a build backend.  (It does not depend on pyproject-hooks.)
>
Thanks,

Is there anything blocking updating pdm?

Scott K

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

#15093

FromScott Talbert <swt@techie.net>
Date2023-08-02 15:40 +0200
Message-ID<GYkeZ-4BfQ-5@gated-at.bofh.it>
In reply to#15091
On Wed, 2 Aug 2023, Scott Kitterman wrote:

> On Tuesday, August 1, 2023 7:36:38 PM EDT Scott Talbert wrote:
>> On Tue, 1 Aug 2023, Scott Kitterman wrote:
>>>> On Tue, 1 Aug 2023, Scott Kitterman wrote:
>>>>> The pep517 package has been renamed pyproject-hooks upstream:
>>>>>
>>>>> https://github.com/pypa/pyproject-hooks
>>>>>
>>>>> It looks like we need this to update python-build to the latest version
>>>>> (which we should definitely do sooner rather than later).
>>>>>
>>>>> Is anyone up  for packaging this?
>>>>>
>>>>> Once it's in the archive we ought to make sure all current users of
>>>>> pep517
>>>>> are switched so we can remove it this cycle.
>>>>
>>>> I'll go ahead and start packaging it.
>>>
>>> Excellent.  PEP517 has a few users that will need to be ported/updated:
>> Initial packaging done, on its way into NEW.
>>
> And it's in Unstable now, so it would be good if people could start updating
> the relevant team packages.  I filed #1042869 for the one package not in DPT.
>
> * python-build (update to new version, needs pyproject-hooks)

I took care of python-build already as a team upload.

Scott T.

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

#15094

FromScott Kitterman <debian@kitterman.com>
Date2023-08-02 15:50 +0200
Message-ID<GYkoG-4BkS-9@gated-at.bofh.it>
In reply to#15093

On August 2, 2023 1:34:32 PM UTC, Scott Talbert <swt@techie.net> wrote:
>On Wed, 2 Aug 2023, Scott Kitterman wrote:
>
>> On Tuesday, August 1, 2023 7:36:38 PM EDT Scott Talbert wrote:
>>> On Tue, 1 Aug 2023, Scott Kitterman wrote:
>>>>> On Tue, 1 Aug 2023, Scott Kitterman wrote:
>>>>>> The pep517 package has been renamed pyproject-hooks upstream:
>>>>>> 
>>>>>> https://github.com/pypa/pyproject-hooks
>>>>>> 
>>>>>> It looks like we need this to update python-build to the latest version
>>>>>> (which we should definitely do sooner rather than later).
>>>>>> 
>>>>>> Is anyone up  for packaging this?
>>>>>> 
>>>>>> Once it's in the archive we ought to make sure all current users of
>>>>>> pep517
>>>>>> are switched so we can remove it this cycle.
>>>>> 
>>>>> I'll go ahead and start packaging it.
>>>> 
>>>> Excellent.  PEP517 has a few users that will need to be ported/updated:
>>> Initial packaging done, on its way into NEW.
>>> 
>> And it's in Unstable now, so it would be good if people could start updating
>> the relevant team packages.  I filed #1042869 for the one package not in DPT.
>> 
>> * python-build (update to new version, needs pyproject-hooks)
>
>I took care of python-build already as a team upload.
>
>Scott T.

Thanks.  I just did check-manifest.

Scott K

[toc] | [prev] | [standalone]

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

csiph-web