[pypy-dev] Python C-API on Windows
Antonio Cuni
anto.cuni at gmail.com
Mon Feb 24 14:15:53 CET 2014
Hi Johan,
the extension module needs to have an extension like *.pypy-22.pyd: this is
to avoid trying to load cpython modules by mistake.
You should use setup.py+distutils to build your module, so that such
details are taken into account automatically.
ciao,
Anto
On Mon, Feb 24, 2014 at 1:50 PM, Johan Råde <johan.rade at gmail.com> wrote:
> Hi Yury,
>
> On Windows a dynamic library, by default, has the extension .dll. But a
> Python extension module must have the extension .pyd, at least under
> CPython. I assumed that the extension should be .pyd under PyPy too.
>
> For what it is worth, here is a link to the Visual Studio solution I used
> to build the extension module
> https://dl.dropboxusercontent.com/u/525329/C-API/Test.zip
>
> --Johan
>
>
>
>
> On 2014-02-24 13:13, Yury V. Zaytsev wrote:
>
>>
>> Back when I was experimenting with CPyExt, I've learned that PyPy will
>> not load foo.so (not sure what the name should be like on Windows) by
>> default, because it doesn't have the right extension, which it will have
>> if it's built with PyPy distutils, but not if you have done this
>> manually with a Makefile.
>>
>> The name should be something like 'foo.pypy-22.so', and the right suffix
>> is defined somewhere in distutils.
>>
>>
>
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> https://mail.python.org/mailman/listinfo/pypy-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20140224/101459ca/attachment.html>
More information about the pypy-dev
mailing list