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 2 #440
Comments
Wrote up a checklist recently for this: https://gist.github.com/sloria/b4a5fc2281f86a5733af198d609c5ab3 |
I wanted to chime in with my $0.02: I wouldn't drop py3.5 support yet because it's the py3 version shipped on several distro versions, notably Ubuntu 16.04. By way of example, if someone is using webargs but they're having trouble upgrading from Ubuntu 16.04 infrastructure to Ubuntu 18.04, then they wouldn't be able to move to the new webargs without either (A) fixing their platform version issues or (B) installing another python version alongside the system python. (Yes, they should fix their problems, but my experience is that by the time you're even talking about being stuck on an old platform version, you're in trouble.) The same argument doesn't apply to forcing the py2 -> py3 transition -- I'm 👍 on dropping py2. |
Yeah, no pressure to remove py35 soon. Can be done later. |
Sounds good. I'm fine keeping support for 3.5 for now. |
Summoning @hugovk again. Would you be willing to tackle this? Just asking. I don't know if you even use webargs. |
Happy to help with Python 3 migration! Please see PR #454 for the first checkbox item: " Drop Python 2". The second checkbox "Make arguments keyword-only where sensible" can follow in another PR. |
With #472 merged, we can call this done! I just did a check on the repo looking for anything python2-related I could find and it came up blank. |
Let's wait on #420 to be merged first to avoid a painful rebase.
Do we also want to drop Python 3.5 ? This can be done in a later major release.
The text was updated successfully, but these errors were encountered: