-
Notifications
You must be signed in to change notification settings - Fork 181
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
MAINT: Datetime deprecations #1330
MAINT: Datetime deprecations #1330
Conversation
0eeb190
to
0427260
Compare
Is there a CI run with 3.12rc1? |
Since Python 3.3, these have been the same. https://docs.python.org/3.3/whatsnew/3.3.html#pep-3151-reworking-the-os-and-io-exception-hierarchy
cbbbb2e
to
89a53d4
Compare
3110183
to
91acbd3
Compare
We do now :) I think this is good to go. |
@@ -198,7 +198,7 @@ def iter_unique(iter): | |||
try: | |||
with open(result_file, 'r') as fp: | |||
benchmarks = json.load(fp) | |||
except (IOError, ValueError): | |||
except (OSError, ValueError): |
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.
I think these should be split into two at some point. The errors are very different, one is that the expected file cannot be found, the other is something else (what?) that fails during discovery.
I think it is fine to drop pypy3.8 testing. The version is not supported upstream, and the test is very slow. Other than one small nit, not really connected to this PR, it all looks good, thanks. I will merge as-is, the two comments can be dealt with elsewhere. |
Closes #1322.