You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am writing to ask for a revert of recent change introduced in 0.23.x releases.
The change I am referring to is located at #4582
I far as I can understand, no API / Bridge change occurred in the PR. No code simplification occurred, only the check for minimal version was patched.
While this change appear straightforward, it induce friction for integrators.
We want to publish new versions, but we are stuck/embarrassed due to the high level constraint (namely python_requires >= 3.7). There is no easy way to mark PyPy 3.7 and 3.8 excluded defacto so that pip or alike wouldn't pick the newer version.
I also understand that the change was motivated due to CI flakyness.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I am writing to ask for a revert of recent change introduced in 0.23.x releases.
The change I am referring to is located at #4582
I far as I can understand, no API / Bridge change occurred in the PR. No code simplification occurred, only the check for minimal version was patched.
While this change appear straightforward, it induce friction for integrators.
We want to publish new versions, but we are stuck/embarrassed due to the high level constraint (namely
python_requires >= 3.7
). There is no easy way to mark PyPy 3.7 and 3.8 excluded defacto so that pip or alike wouldn't pick the newer version.I also understand that the change was motivated due to CI flakyness.
My proposal is as follow:
This would be greatly appreciated.
Regards,
Beta Was this translation helpful? Give feedback.
All reactions