Footnote: I'm pretty sure that the main reason for the renaming was
that we ended up with things like a binding called "zlib.dll" to a
low-level library named "zlib.dll". See e.g. this excerpt from a
ten-year old copy of PC/readme.txt that I had lying around:
/.../ The output file should be called
"spam.dll" or "spam.pyd" (the latter is supported to avoid confusion with a
system library "spam.dll" to which your module could be a Python interface)
in Release mode, or spam_d.dll or spam_d.pyd in Debug mode.
Recent versions of Python no longer support importing DLL:s directly;
you can use imp.get_suffixes() to see what extensions a specific build
supports; here's Python 2.5:
>>> import imp
>>> imp.get_suffixes()
[('.pyd', 'rb', 3), ('.py', 'U', 1), ('.pyw', 'U', 1), ('.pyc', 'rb', 2)]
>>>
</F>
On Tue, Mar 24, 2009 at 7:00 PM, Scott David Daniels
<scott.dani...@acm.org> wrote:
> Bryan Jeal wrote:
> ...
>>
>> After finally getting over the _imaging C module is not installed (even
>> though an _imaging.dll existed - Python2.5 seems to only like _imaging.pyd)
>> and successfully opening and reading a JPEG (I had numerous other errors
>> when I tried to get this working before) file I am so very lost. Please
>> help!
>
> Laura & Edward Cannon told you the simplest way in general.
> However, if you rename you _imaging.dll to be _imaging.pyd, your
> troubles may also be over. Because Microsoft has been trying to
> increase their security by changing the rules about when dlls can
> be loaded (no doubt due to some exciting virii), Python has
> switched to using .pyd for the name of python dlls.
>
> --Scott David Daniels
> scott.dani...@acm.org
>
>
> _______________________________________________
> Image-SIG maillist - image-...@python.org
> http://mail.python.org/mailman/listinfo/image-sig
>
_______________________________________________
Image-SIG maillist - Image-SIG@python.org
http://mail.python.org/mailman/listinfo/image-sig
