<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On Oct 29, 2014, at 7:57 PM, Nick Coghlan <<a href="mailto:ncoghlan@gmail.com" class="">ncoghlan@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><p dir="ltr" class=""><br class="">
On 30 Oct 2014 07:20, "Marcus Smith" <<a href="mailto:qwcode@gmail.com" class="">qwcode@gmail.com</a>> wrote:<br class="">
><br class="">
> yes, I'm partial to a solution like this prior to wheel 2.0 (that I imagine would support additional/custom tags)</p><p dir="ltr" class="">+1 for being able to add additional custom platform tags in the file naming convention from me as well. As Marcus noted earlier, even if you set up distro specific indexes currently, there's nothing built into the tooling to keep you from trying to install (e.g.) a Fedora 21 wheel on RHEL or CentOS 5 (which is highly unlikely to work, given that the core ABIs in RHEL/CentOS 5 are 7 or 8 years old at this point).</p><p dir="ltr" class="">We'd be highly unlikely to flip the switch from "experimental service, use at your own risk" to "fully supported Fedora feature" while that's still the case.</p><p dir="ltr" class="">With arbitrary platform tags, we could inject that into the wheel filenames as part of the build process, and then again when invoking pip.</p><p dir="ltr" class="">That opens things up for us to figure out how to best flag compatibility on the distro side, without committing to a specific approach upstream (not yet, anyway).</p><p dir="ltr" class="">An alternative approach would be to add an "additional wheel suffix" setting for pip that allowed us to have names with endings like ".fc21.whl" or ".el7.whl" recognised as valid wheel files.</p><p dir="ltr" class="">I'm not that worried about the exact details though - the main feature I'd like is the ability to create wheel files that pip will ignore by default, but will accept if I specifically tell it what to look for.</p><div class=""><br class=""></div></div></blockquote><br class=""></div><div>Do we plan for this to be allowed to upload to PyPI proper? These custom tags?</div><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">---</div><div class="">Donald Stufft</div><div class="">PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA</div></div></div>
</div>
<br class=""></body></html>