-
Notifications
You must be signed in to change notification settings - Fork 90
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
Deprecate Python 3.6 & 3.7; get CI working again #270
Conversation
Thanks for the PR. It looks like the CI is broken for the repo at the moment. I will have to look into fixing this before I can merge! |
Seems like issues with some CI running on older python 3.7. I'd recommend dropping support (it's at EOL in 2 months anyways) |
@BrianPugh Could you submit a PR to drop support? I cannot approve my own PRs, so would need to wait until another maintainer is available to get it through if I do it... |
on it 👍 |
937eed1
to
2f1b5df
Compare
2f1b5df
to
a1b9fe8
Compare
Thanks, much appreciated. Would you be able to submit a separate PR for it? |
I'm still working on fixing this up, I'll let you know when it's ready. Why the separate PR? |
It's good practice to have only one change per PR. It also means the commit history has an entry per change. Finally, it means changes are not missed when the changelog is written. |
yeah, but in this case it's kind of complicated since CI is broken.
So like this could sort of be broken up into multiple PRs, but it'd be a lot more work for basically no benefit since the goal is to get everything working again with community-supported versions of python. |
Fair enough. Keep it in this one, and I'll make sure the commit description contains all the changes. Tag me when you're ready for me to review/merge :) |
a61f750
to
dfa8c9c
Compare
@kiancross I think this is getting close to complete. What I've done so far:
What I can't figure out:
|
Thanks for all the help. If possible, try to keep the PR as limited in scope as possible (i.e., only what is needed to get CI working again).
Try changing the following URL Line 36 in 87a891c
to https://python-prompt-toolkit.readthedocs.io/en/3.0.36/ If that doesn't work, I can take a look, but probs won't have time for a couple of weeks. Another problem we have is that the 3.6 CI runs are marked as required, and I can't overrule this. @tmbo Can you remove all CI requirements from the branch rules for now, and I will provide a list of which ones to add back once all the CI issues are fixed? |
All the changes so far are the minimum necessary to get CI working (outside of just disabling type checking).
That worked! looks like some codecov issues that i should be able to tack in the next day or two. |
@kiancross so I think this all works, so I'd say approve the workflow to run and we'll see, but I think i tested it about as far as I can from my side. |
The MacOS breakage might be because Poetry also needs updating (see #266). |
updated; the cache might need to be cleared for it to take effect, though. |
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.
Ok, this is looking good! Thanks for all your help. I've left some comments/questions below. Can you also update the title of this PR to reflect it's current state and provide a list of changes in the description? I will use this for the commit when merging.
This is sorted now too, so almost ready to merge! |
my quick todo list (gotta run for now):
|
Finally circled back around on this; @kiancross I believe this is ready for another review! |
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.
All looks good, thanks a lot for all your work!
Is it possible to support the latest version of prompt_toolkit yet? |
maybe it needs prompt-toolkit-3.0.40, not yet released , with this prompt-toolkit/python-prompt-toolkit#1799 |
Change Log
-sl
with current--force-single-line-imports
.merge_styles
prompt_toolkit
version to be<=3.0.36
because3.0.37
has introduced some event-loop-related bug.make clean
will now also clean the docs.Original Post
What is the problem that this PR addresses?
How did you solve it?
pre-commit autoupdate
to update all plugins; fixing minor linting issues in changes of Black.Checklist