On 31 August 2017 at 14:22, xoviat <xov...@gmail.com> wrote: > This appears to be related to https://github.com/pypa/pip/pull/3225, where > pip would generate overbroad wheel names in the cache. So to proceed on this > issue, setuptools will assume that generated wheels are valid for the > specific python implementation only (eg. wheels generated for CPython will > not be valid for pypy). > > 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), 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. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
