[Wheel-builders] [RFC] Proposal for packaging native libraries into Python wheels

[Donald Stufft]

> On Apr 11, 2016, at 9:06 AM, Nathaniel Smith <njs at pobox.com <mailto:njs at pobox.com>> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/wheel-builders/attachments/20160411/2e7c2311/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/wheel-builders/attachments/20160411/2e7c2311/attachment-0001.sig>