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
Py2to3: Futurize stage 2 #406
Comments
Need to think about these
|
Remaining ones, probably for Q3 and need to do str-unicode ones more carefully. libfuturize.fixes.fix_unicode_keep_u |
This includes libfuturize.fixes.fix_future_standard_library_urllib
Remaining (in libfuturize.fixes.fix_object, didn't do ndb_patcher since it is going away): libfuturize.fixes.fix_unicode_keep_u |
i'll tackle the unicode/str conversion |
Apply libfuturize.fixes.fix_future_standard_library and libfuturize.fixes.fix_basestring.
For future, need to careful of any migration change in docker/ dir, example breakage due to 6d9f9e7#diff-f1db2c4f1d1b92aef6e74abff3119154 (my bad :() since we don't have future lib during start_host.py time. also got noticed when we updated host image. |
Just for tracking, we include everything now except libfuturize.fixes.fix_unicode_keep_u and libfuturize.fixes.fix_future_builtins (these need more work, will come later). minor exclusion is ndb_patcher which will go away soon. To replicate / reapply fixes, do |
All the futurize fixes were completed. |
As part of Python 3 migration (#183)
git ls-files "*.py" | xargs futurize -w -n --stage2
obviously not as simple. need to be done in steps, and str and unicode fixes are the more tricky ones.
The text was updated successfully, but these errors were encountered: