-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add xfails for CPython 3.13.0a5 #3371
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.
Looks good to unblock CI, do we only need this until trustme creates a new release?
@@ -77,6 +78,10 @@ def teardown_class(cls) -> None: | |||
super().teardown_class() | |||
shutil.rmtree(cls.certs_dir) | |||
|
|||
@pytest.mark.xfail( |
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.
There's a lot of duplication, can we create a marker and reuse it?
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.
Sure
When there is a new trustme release, we can pin the package to it instead of to the commit The xfails can be dropped when Python 3.13 alpha 6 is available; the expected release date is April 9th + maybe a few days for GitHub Actions to provide the new version |
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.
LGTM
Resolves #3366
xfails in
test/with_dummyserver/test_proxy_poolmanager.py
can be dropped when CPython 3.13.0a6 is available.