-
-
Notifications
You must be signed in to change notification settings - Fork 662
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
Fix CI (for latest pytest version) #2015
Conversation
The CI failure on commit b9b3b2f is coming from our jupyter notebook test. I've opened an issue against the |
7e07044
to
c2a7d8f
Compare
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! one minor comment :)
_upgrade_basic(session) | ||
_install_pytest(session) |
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.
nit: since we need to always install pytest along with the upgrade_basic, could we merge them into one method, something like install_basic?
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 had the same thought, but it turns out that the lint
and lint_plugins
nox sessions do not require installing pytest (but they do still use upgrade_basic).
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 have just opened PR #2016 which only pins pytest for the jupyter notebook session. I'm thinking of closing this PR in favor of that one. What do you think?
(One benefit of not pinning pytest is that the new pytest version should allow us to move forward with python3.10 support, which is currently blocked).
A new pytest release came out earlier today.