Carol,
I'm "happy" with Steve's position. Fundamentally I am at fault for
assuming that a combination of the stable ABI and Python's deprecation
policy meant that I could assume that a wheel for Python v3.x would
continue to work for v3.x+1. For this particular change I don't see how
a normal deprecation warning could have been implemented. The only
alternative would have been to delay the implementation for v3.9 and
have loud warnings in the v3.8 docs about the upcoming change.
Phil
On 23/06/2019 00:06, Carol Willing wrote:
Hi Phil,
Thanks for trying the beta. Please file this as an issue at
bugs.python.org. Doing so would be helpful for folks who can look into
the issue.
Thanks,
Carol
On 6/22/19 2:04 PM, Phil Thompson wrote:
The implementation of issue 36085 breaks PyQt on Windows as it relies
on PATH to find the Qt DLLs. The problem is that PyQt is built using
the stable ABI and a single wheel is supposed to support all versions
of Python starting with v3.5. On the assumption (perhaps naive) that
using the stable ABI would avoid future compatibility issues, the
existing PyPI wheels have long been tagged with cp38.
Was this issue considered at the time? What is the official view?
Thanks,
Phil
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/YFNKFRJGNM25VUGDJ5PVCQM4WPLZU6J7/
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/VWIWASHPBMLQDS7PQX3LXILT56Q2KCPO/
