-
Notifications
You must be signed in to change notification settings - Fork 106
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
Drop Python 3.6 #535
Drop Python 3.6 #535
Conversation
Failing on an unrelated black/click error? |
@michaeloliverx Looks similar to this: encode/httpx#2097 (comment) Also note: encode/httpx#2097 (comment) |
@michaeloliverx From #536 it looks like 3.6 CI is essentially broken because a bunch of core tooling have already dropped support. We might want to merge it into this PR so we don't try to upgrade tooling that wouldn't work on 3.6 anyway. |
@florimondmanca - Make sense, yup. Is upgrading the pin on |
It looks like no..
I will try and bump |
Okay were are stuck in the same place as #536 now.. If anyone has extra bandwidth feel free to add to this PR if not I can look again later. |
Right, so we can either unpin |
Unpinned |
This reverts commit 0f5115c.
@michaeloliverx I'm seeing something weird - mkdocs 1.2.4 (or 1.3.0) should have resolved the jinja2 issue but the one we're seeing ( For now I'm attempting to pin jinja2 to 3.9.2 and see if it passes CI. Also pinning flake8 to a version before it pinned importlib-metadata on <3.8. Now httpbin is broken! 😆 |
@florimondmanca I see green! |
I'm happy to merge this, though the triple stitch on three different package compatibility issues is a bit disappointing. We can merge and review these when things settle down for either of the three cases... What do people think? |
I'm okay with it, yup. |
Added a note about 3.7+ |
Thanks so much @michaeloliverx. Approved the PR, feel free to merge whenever ready. |
Closes: #515