-
Notifications
You must be signed in to change notification settings - Fork 57
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
base: main
Are you sure you want to change the base?
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.
* Student schedule fixes * make tests parallel; don't render latex response as http response * add required argument to programprintables test * add required program argument to allclassesselection tests * don't run tests in parallel yet --------- Co-authored-by: William Gearty <willgearty@gmail.com>
…ESP-Website into migration-to-python3
* Prevent program with duplicate name/URL and update account name * Show form errors in form instead of as a Whoops page
Migrate the codebase to Python 3 (currently 3.7, aiming for higher once we bump Django and other packages)