-
-
Notifications
You must be signed in to change notification settings - Fork 635
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Constrain the ICs in the coverage py integration tests. #21540
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
(Wondering out loud if we need some sort of companion to all_major_minor_python_versions
like all_major_minor_python_versions_with_supported_pip
or something, or if if even less effort should be expended don EOL Pythons)
They are failing on release branches on the new ARM64 AMIs that have Python 3.7-3.13 on them, because there is no pip that can be installed on all those versions.
They are failing on release branches on the new ARM64 AMIs that have Python 3.7-3.13 on them, because there is no pip that can be installed on all those versions.
They are failing on release branches on the new ARM64 AMIs that have Python 3.7-3.13 on them, because there is no pip that can be installed on all those versions.
Well, I think the real solution is to eliminate loose interpreter constraints, and require you to select one or more specific interpreters for which we generate complete_platform files... |
Follow up to #21540, which alas only tackled half the tests (and those do indeed pass on the new ARM images, so this change should now cause the rest to pass).
Follow up to #21540, which alas only tackled half the tests (and those do indeed pass on the new ARM images, so this change should now cause the rest to pass).
Follow up to #21540, which alas only tackled half the tests (and those do indeed pass on the new ARM images, so this change should now cause the rest to pass).
Follow up to #21540, which alas only tackled half the tests (and those do indeed pass on the new ARM images, so this change should now cause the rest to pass).
They are failing on release branches on the new ARM64 AMIs that
have Python 3.7-3.13 on them, because there is no pip that can be
installed on all those versions.