Re: disable building wheel for a package

> so the people benefiting
> are those who want a supported API for that functionality, and it
> seems only reasonable to expect them to do the job of moving the code,
> rather than expecting the pip developers to do so.

This is where I think we disagree and I feel the rhetoric is a bit harmful -- personally I don't benefit much at all, I actually don't think any individual maintainer inside the PyPA benefits much beyond having a new project to maintain, so the 'helps me vs helps you' framing isn't really the point.  If it strictly helped me to add a project to my list of things to maintain I would have done that already. The real issue here is that we all have different implementations and they create non-uniform / disjointed user experiences.  Converging on a set of common elements to extract seems like step 1

I am fairly new to the PyPA, and I don't know how any of these processes actually work.  But I do know that painting this as "us vs you" when my interest actually in helping the user of packaging tools is causing a disconnect for me anytime we engage on this -- and I'm not asking you to tackle any of this yourself, except possibly review someone's PR down the road to swap out some internals. 

Dan Ryan
gh: @techalchemy // e: [email protected]


> -----Original Message-----
> From: Paul Moore [mailto:[email protected]]
> Sent: Tuesday, September 18, 2018 6:09 PM
> To: Donald Stufft
> Cc: Dan Ryan; Thomas Kluyver; Distutils
> Subject: Re: [Distutils] disable building wheel for a package
> 
> Agreed. Furthermore, if people are of the opinion that pip's
> implementation is suitable, copying it out into packaging is likely
> not going to be at all controversial. Of course, it's not going to be
> any direct advantage to pip if that's done (we get the same
> functionality, just in a different place), so the people benefiting
> are those who want a supported API for that functionality, and it
> seems only reasonable to expect them to do the job of moving the code,
> rather than expecting the pip developers to do so.
> 
> In the case of pip's location code, more time has likely been spent
> discussing the problem than it would actually take to make the change.
> (Of course, no one person has spent that much time in discussions, but
> it adds up - coding doesn't work that way sadly).
> 
> Paul
> 

--
Distutils-SIG mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/
Message archived at https://mail.python.org/mm3/archives/list/[email protected]/message/AQNFQBR3VHYCMVQRTMKAE4PIEKOP7SOT/