[Distutils] cffi & Py_LIMITED_API

Nick Coghlan ncoghlan at gmail.com
Tue Aug 2 04:02:23 EDT 2016

On 2 August 2016 at 02:24, Daniel Holth <dholth at gmail.com> wrote:
> On Mon, Aug 1, 2016 at 12:01 PM Steve Dower <steve.dower at python.org> wrote:
>> The DLL tag on Windows will have to just be ".pyd" if you want to
>> support back prior to 3.5. In 3.5 you can use ".cp35-win32.pyd" or
>> ".cp35-win_amd64.pyd" and the importer will prefer that DLL over a plain
>> ".pyd", but my proposal to also support ".cp3-${PLAT}.pyd" here didn't
>> make it.
>> The wheel tag is more important than the DLL tag. (Possibly you're not
>> even suggesting changing the DLL name at all and just passing the flag
>> through for the build option? Hard to tell from the discussion.)
> I'm sure we are interpolating from Linux, where you'd be looking at
> extensions .cpython-35m-x86_64-linux-gnu.so versus .abi3.so. But any DLL
> extension that the target CPythons will agree to load, plus an appropriate
> wheel tag, should be sufficient for our use case.

Right, on *nix the SO names already include the SOABI details by
default, so we really do want to change those to something less
explicit, but I'm not sure it's even possible to using a completely
unqualified SO name even if we wanted to.

On Windows, if we have to rely on dropping any ABI indicated from the
DLL entirely, we can leave with - pip should keep things from
colliding too badly.


Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Distutils-SIG mailing list