<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"><meta http-equiv="Content-Type" content="text/html charset=utf-8"><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 11, 2016, at 9:06 AM, Nathaniel Smith <<a href="mailto:njs@pobox.com" class="">njs@pobox.com</a>> wrote:</div><div class=""><br class=""><p dir="ltr" class="">The indirection isn't needed to make it executable, it's needed so that we have a chance to munge LD_LIBRARY_PATH before loading the real binary.</p></div></blockquote><div><br class=""></div><div>Oh right, I missed that part. I blame just waking up.</div><div><br class=""></div><blockquote type="cite" class=""><br class=""><p dir="ltr" class="">Huh, that's an interesting and slightly terrifying idea. Can a wheel drop a .pth file into site-packages? I mean, does that even work technically?</p><div class=""><br class=""></div></blockquote><div><br class=""></div>Yes. A .pth file is no different than any other file as far as wheels are concerned. If you have a pynativelib.pth in your wheel then it’ll get installed.<br class=""><blockquote type="cite" class=""><p dir="ltr" class=""><br class=""></p><p dir="ltr" class="">I think this hits the bootstrap problem: who's going to modify sys.meta_path before our package starts loading?</p><div class=""><br class=""></div></blockquote><div><br class=""></div>The .pth file that the pynativelib wheel ships.<br class=""></div><br class=""><div class="">
<br class="">-----------------<br class="">Donald Stufft<br class="">PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
</div>
<br class=""></body></html>