/usr/local/lib/python3.9/site-packages/libfuturize/fixes
NameSizeModeActions
__pycache__/-0755rm
fix_absolute_import.py31400644editdlrm
fix_add__future__imports_except_unicode_literals.py6620644editdlrm
fix_basestring.py3940644editdlrm
fix_bytes.py6850644editdlrm
fix_cmp.py7010644editdlrm
fix_division.py2280644editdlrm
fix_division_safe.py36310644editdlrm
fix_execfile.py9210644editdlrm
fix_future_builtins.py20270644editdlrm
fix_future_standard_library.py7330644editdlrm
fix_future_standard_library_urllib.py10010644editdlrm
fix_input.py6870644editdlrm
fix_metaclass.py95700644editdlrm
fix_next_call.py31580644editdlrm
fix_object.py4070644editdlrm
fix_oldstr_wrap.py12140644editdlrm
fix_order___future__imports.py8290644editdlrm
fix_print.py38810644editdlrm
fix_print_with_import.py7350644editdlrm
fix_raise.py39040644editdlrm
fix_remove_old__future__imports.py8510644editdlrm
fix_unicode_keep_u.py7790644editdlrm
fix_unicode_literals_import.py3670644editdlrm
fix_UserDict.py38400644editdlrm
fix_xrange_with_import.py4790644editdlrm
__init__.py52360644editdlrm
Edit: /usr/local/lib/python3.9/site-packages/libfuturize/fixes/fix_unicode_keep_u.py (779B)
"""Fixer that changes unicode to str and unichr to chr, but -- unlike the lib2to3 fix_unicode.py fixer, does not change u"..." into "...". The reason is that Py3.3+ supports the u"..." string prefix, and, if present, the prefix may provide useful information for disambiguating between byte strings and unicode strings, which is often the hardest part of the porting task. """ from lib2to3.pgen2 import token from lib2to3 import fixer_base _mapping = {u"unichr" : u"chr", u"unicode" : u"str"} class FixUnicodeKeepU(fixer_base.BaseFix): BM_compatible = True PATTERN = "'unicode' | 'unichr'" def transform(self, node, results): if node.type == token.NAME: new = node.clone() new.value = _mapping[node.value] return new