3 ms·
It doesn't work against precompiled native extensions, but it does work against wrappers against separate native libraries, like a database driver or libpng or
by chrisseaton 12y ago
It doesn't work against precompiled native extensions, but it does work against wrappers against separate native libraries, like a database driver or libpng or something like that. The C interpreter can interface with native code, and the JIT has special support for making those calls very fast [1] (it's not like JNI, for example).
So the only thing it doesn't work for is precompiled native extensions where you don't have these source code - so maybe a proprietary C extension. Do you get many of those in practice?
[1] http://dl.acm.org/citation.cfm?id=2500832 http://dl.acm.org/citation.cfm?id=2500832
- masklinn 12y ago> So the only thing it doesn't work for is precompiled native extensions where you don't have these source code Or you can't build it because you're on windows, or the extension was installed precompiled by the package manager (on Python, that's exactly one of the use case for wheels, I don't think wheels ship C code ever), or the extension is coded in non-C (which is very much explicitly supported by CPython: https://docs.python.org/3/extending/extending.html#writing-extensions-in-c https://docs.python.org/3/extending/extending.html#writing-e...)
- maxerickson 12y agoMicrosoft has done work to make the Windows situation at least incrementally better: https://mail.python.org/pipermail/distutils-sig/2014-September/024885.html https://mail.python.org/pipermail/distutils-sig/2014-Septemb... (I'm crassly attaching a bit of information to your post more than trying to respond to anything in it)