ok
Direktori : /usr/lib64/python3.6/test/support/__pycache__/ |
Current File : //usr/lib64/python3.6/test/support/__pycache__/script_helper.cpython-36.pyc |
3 ��d�) � @ s d dl Z d dlZd dlZd dlZd dlZd dlZd dlZd dlZd dlZd dl Z d dl Z d dlmZ d dl mZmZ dadd� ZG dd� de jdd#��Zdd� Zd d� Zdd� Zdd� Zejejd�dd�Zdd� Zd$dd�Zd%dd�Zd&dd�Zd'd!d"�ZdS )(� N)�source_from_cache)�make_legacy_pyc�strip_python_stderrc C sV t dkrRdtjkrda dS ytjtjdddg� W n tjk rL da Y nX da t S )a Returns True if our sys.executable interpreter requires environment variables in order to be able to run at all. This is designed to be used with @unittest.skipIf() to annotate tests that need to use an assert_python*() function to launch an isolated mode (-I) or no environment mode (-E) sub-interpreter process. A normal build & test does not run into this situation but it can happen when trying to run the standard library test suite from an interpreter that doesn't have an obvious home with Python's current home finding logic. Setting PYTHONHOME is one way to get most of the testsuite to run in that situation. PYTHONPATH or PYTHONUSERSITE are other common environment variables that might impact whether or not the interpreter can start. NZ PYTHONHOMETz-Ez-czimport sys; sys.exit(0)F)�$__cached_interp_requires_environment�os�environ� subprocessZ check_call�sys� executableZCalledProcessError� r r �%/usr/lib64/python3.6/script_helper.py� interpreter_requires_environment s r c @ s e Zd ZdZdd� ZdS )�_PythonRunResultz2Helper for reporting Python subprocess run resultsc C s� d }| j | j }}t|�|kr0d|| d� }t|�|krNd|| d� }|jdd�j� }|jdd�j� }td| j|||f ��dS ) z4Provide helpful details about failed subcommand runs�P �d s (... truncated stdout ...)Ns (... truncated stderr ...)�ascii�replacezRProcess return code is %d command line: %r stdout: --- %s --- stderr: --- %s ---i@ )�out�err�len�decode�rstrip�AssertionError�rc)�self�cmd_line�maxlenr r r r r �fail>