Mailing List Archive

how to motivate upstream to use PEP517?
I've filed a bug to wsgi-intercept to switch to PEP517 and their answer
was " The current build system works".
How to motivate them?
What's the real killer feature?
Is something going to be deprecated soon that will force a switch?
Re: how to motivate upstream to use PEP517? [ In reply to ]
On 17/05/2022 11:51, Alessandro Barbieri wrote:
> I've filed a bug to wsgi-intercept to switch to  PEP517 and their answer
> was " The current build system works".
> How to motivate them?
> What's the real killer feature?
> Is something going to be deprecated soon that will force a switch?

What's PEP517? What are you talking about? What's the problem?

Cheers,
Wol
Re: how to motivate upstream to use PEP517? [ In reply to ]
Il giorno mar 17 mag 2022 alle ore 21:04 Wol <antlists@youngman.org.uk> ha
scritto:

> On 17/05/2022 11:51, Alessandro Barbieri wrote:
> > I've filed a bug to wsgi-intercept to switch to PEP517 and their answer
> > was " The current build system works".
> > How to motivate them?
> > What's the real killer feature?
> > Is something going to be deprecated soon that will force a switch?
>
> What's PEP517? What are you talking about? What's the problem?
>
> Cheers,
> Wol
>
>
It's the new build system for python packages
https://peps.python.org/pep-0517/