ok
Direktori : /opt/cloudlinux/venv/lib/python3.11/site-packages/libfuturize/__pycache__/ |
Current File : //opt/cloudlinux/venv/lib/python3.11/site-packages/libfuturize/__pycache__/main.cpython-311.pyc |
� �܋f�5 � � � d Z ddlmZmZmZ ddlZddlmZ ddlZddl Z ddl Z ddlZddlm Z mZ ddlmZ ddlmZmZmZmZ dZd d �ZdS )a� futurize: automatic conversion to clean 2/3 code using ``python-future`` ====================================================================== Like Armin Ronacher's modernize.py, ``futurize`` attempts to produce clean standard Python 3 code that runs on both Py2 and Py3. One pass -------- Use it like this on Python 2 code: $ futurize --verbose mypython2script.py This will attempt to port the code to standard Py3 code that also provides Py2 compatibility with the help of the right imports from ``future``. To write changes to the files, use the -w flag. Two stages ---------- The ``futurize`` script can also be called in two separate stages. First: $ futurize --stage1 mypython2script.py This produces more modern Python 2 code that is not yet compatible with Python 3. The tests should still run and the diff should be uncontroversial to apply to most Python projects that are willing to drop support for Python 2.5 and lower. After this, the recommended approach is to explicitly mark all strings that must be byte-strings with a b'' prefix and all text (unicode) strings with a u'' prefix, and then invoke the second stage of Python 2 to 2/3 conversion with:: $ futurize --stage2 mypython2script.py Stage 2 adds a dependency on ``future``. It converts most remaining Python 2-specific code to Python 3 code and adds appropriate imports from ``future`` to restore Py2 support. The command above leaves all unadorned string literals as native strings (byte-strings on Py2, unicode strings on Py3). If instead you would like all unadorned string literals to be promoted to unicode, you can also pass this flag: $ futurize --stage2 --unicode-literals mypython2script.py This adds the declaration ``from __future__ import unicode_literals`` to the top of each file, which implicitly declares all unadorned string literals to be unicode strings (``unicode`` on Py2). All imports ----------- The --all-imports option forces adding all ``__future__`` imports, ``builtins`` imports, and standard library aliases, even if they don't seem necessary for the current state of each module. (This can simplify testing, and can reduce the need to think about Py2 compatibility when editing the code further.) � )�absolute_import�print_function�unicode_literalsN)�__version__)�warn�StdoutRefactoringTool)�refactor)�lib2to3_fix_names_stage1�lib2to3_fix_names_stage2�libfuturize_fix_names_stage1�libfuturize_fix_names_stage2zlibfuturize.fixesc �t �� t j d�� � }|� dddd�� � |� dd dd �� � |� dddd �� � |� dddd�� � |� dddd�� � |� dddd�� � |� dddg d�� � |� ddddd d!�"� � |� d#d$dg d%�� � |� d&d'dd(�� � |� d)d*dd+�� � |� d,d-dd.�� � |� d/dd0�� � |� d1d2dd3�� � |� d4d5dd6d7�� � |� d8d9dd:d;d<�=� � |� d>d?dd@�� � |� dAdd:d;dB�=� � i }d6}|� | � � \ }} |j r"dC|dD<