> On Apr 11, 2016, at 9:06 AM, Nathaniel Smith <[email protected] > <mailto:[email protected]>> wrote: > > 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. >
Oh right, I missed that part. I blame just waking up. > > 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? > > 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. > > I think this hits the bootstrap problem: who's going to modify sys.meta_path > before our package starts loading? > > The .pth file that the pynativelib wheel ships. ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Wheel-builders mailing list [email protected] https://mail.python.org/mailman/listinfo/wheel-builders
