Re: Updating python-build/getting rid of pep517
On 2023-08-02 09 h 23, Éric Araujo 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.) Cheers I see pdm-pep517 is still a complete package (as opposed to being a virtual package redirecting to pdm-backend). What's the plan for this? I'm asking, since at the moment in Lintian, when we find a `build-backend = "pdm.pep517.api"` line in pyproject.toml, we are recommending people build-depend on python3-pdm-pep517. Should I change something? -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_0xE1E5457C8BAD4113.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: Updating python-build/getting rid of pep517
On August 2, 2023 1:23:15 PM UTC, "Éric Araujo" 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
Re: Updating python-build/getting rid of pep517
On August 2, 2023 1:34:32 PM UTC, Scott Talbert 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
Re: Updating python-build/getting rid of pep517
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.
Re: Updating python-build/getting rid of pep517
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
Re: Updating python-build/getting rid of pep517
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 signature.asc Description: This is a digitally signed message part.
Re: Updating python-build/getting rid of pep517
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.
Re: Updating python-build/getting rid of pep517
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 signature.asc Description: This is a digitally signed message part.
Re: Updating python-build/getting rid of pep517
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
Updating python-build/getting rid of pep517
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 signature.asc Description: This is a digitally signed message part.
