<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Jan 21, 2016 at 7:32 PM, Nick Coghlan <span dir="ltr"><<a href="mailto:ncoghlan@gmail.com" target="_blank">ncoghlan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><div class="h5"><br></div></div>
However, it does suggest a possible alternative approach to naming<br>
these compatibility subsets: what if the name of this particular<br>
platform compatibility tag was something like "linux-sciabi1", rather<br>
than "manylinux1"?<br></blockquote><div><br></div><div>That's an interesting idea, but I personally don't see the manylinux1 list as particularly</div><div>"scientific". If anything, I'd call it "minimal".</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
That way, if someone later wanted to propose "linux-guiabi1" or<br>
"linux-audioabi1" or "linux-videoabi1", that could be done.</blockquote></div><br><div>This would be something, but if we want to have Linux binary wheels that tightly integrate</div><div>with system libraries for certain use cases, the <i>really </i>valuable thing would be <a href="https://github.com/pypa/interoperability-peps/pull/30/files">https://github.com/pypa/interoperability-peps/pull/30/files</a>, more so than specific ABI tags, IMO.</div><div><br></div><div class="gmail_signature"><div dir="ltr"><div>-Robert</div></div></div>
</div></div>