[Pythonmac-SIG] Python C extensions that depend on dynamic libraries

[Bob Ippolito]

On Jan 12, 2004, at 3:24 AM, Ronald Oussoren wrote:

>
> On 12 jan 2004, at 1:37, Bob Ippolito wrote:
>>> I think .bundle is likely to cause more confusion than not; something
>>> with Python in the name (akin to .pyd on Windows) seems like a much
>>> better idea, perhaps ".pyext" or ".pymod"?
>>
>> The only people that use something "non-standard" are the Java 
>> people.. Everyone else uses .bundle or .so.
>
> I agree with Nicholas on this, using .bundle as the extention for 
> extention modules will very likely cause confusion because the term 
> bundle is usually used for specially structured folders (app bundles 
> and the like).

Well, it's pretty obvious they're not folders, so I wouldn't be 
confused.

Just as a semi-but-not-really-serious idea:  I wouldn't complain if 
they *were* folders (CFBundle-type-bundles) on the Mac.  Think about 
it, we could embed the particular version of Python and OS 
compatibility matrix in the Info.plist, throw in some fun external data 
into Resources, put required dylibs/frameworks in Frameworks (and the 
Python runtime could jigger the appropriate dyld incantations to make 
them load properly), use a higher level plugin API then raw dyld, 
whatever.  It's a metadata party, and everyone is invited.

> What's wrong with using '.so' as the extention?

.so probably implies MH_DYLIB?  I don't really have a problem with .so. 
  It's ".pyext" that I don't really like.

-bob
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2357 bytes
Desc: not available
Url : http://mail.python.org/pipermail/pythonmac-sig/attachments/20040112/b84c388a/smime.bin