-
Notifications
You must be signed in to change notification settings - Fork 58
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
Migration to Python3 #3616
Migration to Python3 #3616
Conversation
full command/config: python -m modernize --no-diffs --write --nobackups --six-unicode --enforce --fix=default --fix=libmodernize.fixes.fix_open -f classic_division -f open -f idioms -f set_literal -f ws_comma .
Regarding Python 3.7, its end-of-life is only a few months way (2023-06-27). |
Good catch, Ted. I think we want to avoid upgrading Django in this PR (the main limiting library), but we should make a separate issue to bump Django as soon as possible. Then we can bump to a current version of Python. Only potential reason I can see to do it sooner is that this tool https://docs.python.org/3.10/library/functools.html#functools.cmp_to_key buys us a lot of ground with the |
Change 'is' to '==' when used with a literal 'png' drop database test_test_django in the before_script
Since __name__ requires `str` type, also add a `str` cast in create_membership_method.
For the record, once the tests are fixed up and everything, you can test locally by running |
…d other minor USC fixes)
change string representation of types to be correct and use string as default so that errors will emerge when admins look at answers rather than when students/teachers submit them
…limited/ESP-Website into migration-to-python3
🤩 |
Migrate the codebase to Python 3 (currently 3.7, aiming for higher once we bump Django and other packages)
Fixes #2576.