Will do. Better to hash this out sooner than later. On Aug 31, 2017 12:36 AM, "Nathaniel Smith" <n...@pobox.com> wrote:
> On Wed, Aug 30, 2017 at 9:56 PM, Nick Coghlan <ncogh...@gmail.com> wrote: > > On 31 August 2017 at 14:22, xoviat <xov...@gmail.com> wrote: > >> Again, let me repeat that: wheels generated using setuptools are valid > for > >> CPython only if build on CPython. This is not the current setuptools > >> behavior but will be for all setuptools build backend calls (I assume > legacy > >> will remain the same). > > > > While I do think your proposal would work (on the assumption that > > folks aren't use "pip wheel" to generate their wheel files for > > upload), > > I use 'pip wheel' to generate wheel files for upload... (I like to > generate an sdist and then build a wheel from that, and 'pip wheel > sdist.tar.gz' is more convenient than manually unpacking and running > bdist_wheel. ) > > > an alternative approach with a lower risk of unintended side > > effects would be for *pip* to either rename the autobuilt file before > > adding it to the cache, or else to adjust its caching strategy a bit > > to internally separate a shared wheel download cache from > > per-interpreter-compatibility-tag caches for locally built wheel > > files. > > +1 > > -n > > -- > Nathaniel J. Smith -- https://vorpus.org >
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
