Steve Dower added the comment:
> Could you explain what replacing the _d suffix with a "d" ABI flag
> would break ?
It breaks consistency with python_d.exe and python35_d.dll, mainly, and those
are not going to change (specifically, python.exe and python35.dll are not
going to change, and so there's no point changing the debug versions any more
than with _d).
It would also break consistency with untagged PYDs, which are still supported
but still need to distinguish between debug and release builds. Currently the
accepted suffixes are "_d.cp35-{plat}.pyd" and "_d.pyd". While we could start
requiring at least "cp3d" as the API tag, that would break a lot of development
environments for no gain.
So basically, I see compelling reasons for allowing the platform in the name,
good enough reasons for the version, but not good enough reasons for changing
the existing debug tag (and no reason for the m flag at all).
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue22980>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
