Файловый менеджер - Редактировать - /opt/imh-python/lib/python3.9/site-packages/fabric/__pycache__/operations.cpython-39.pyc
Ðазад
a {�h�� � @ s d Z ddlZddlZddlZddlZddlZddlZddlZddlZddl Z ddl m Z ddl m Z ddl mZmZ ddlmZmZmZmZmZ ddlmZmZ ddlm Z m Z m Z dd l m Z dd l!m"Z"m#Z#m$Z$m%Z%m&Z& dd l'm(Z( dd l)m*Z*m+Z+m,Z,m-Z-m.Z.m/Z/m0Z0 d d� Z1G dd� de2�Z3G dd� de4�Z5G dd� de6�Z7dd� Z8d<dd�Z9e d=d d ��Z:e d>d d ��Z;d d!� Z<d?d"d#�Z=d@d$d%�Z>d&d'� Z?dAd(d)�Z@dBd*d+�ZAe dCd,d-��ZBed.d/� �ZCdDd0d1�ZDe dEd2d3��ZEe dFd4d5��ZFdGd7d8�ZGe dHd;d:��ZHdS )IzQ Functions to be used in fabfiles and other non-core code, such as run()/sudo(). � N)�glob)�deque)�closing�contextmanager)�settings� char_buffered�hide�quiet� warn_only)� output_loop� input_loop)� needs_host�ssh� ssh_config)�SFTP)�env� connections�output�win32�default_channel)� ThreadHandler)�abort�error�handle_prompt_abort�indent� _pty_size�warn� apply_lcwdc C s dD ]}| � |d| �} q| S )z� Escape double quotes, backticks and dollar signs in given ``string``. For example:: >>> _shell_escape('abc$') 'abc\\$' >>> _shell_escape('"') '\\"' )�"�$�`z\%s)�replace)�string�char� r$ ��/root/rpmbuild/BUILDROOT/imh-python39-modules-3.9.7-92.el8.x86_64/opt/imh-python/lib/python3.9/site-packages/fabric/operations.py� _shell_escape s r& c @ s e Zd ZdZedd� �ZdS )� _stdoutStringzE Simple string subclass to allow arbitrary attribute access. c C s t | �S �N)�str��selfr$ r$ r% �stdout2 s z_stdoutString.stdoutN��__name__� __module__� __qualname__�__doc__�propertyr, r$ r$ r$ r% r' . s r' c @ s e Zd ZdZedd� �ZdS )� _stdoutByteszD Simple bytes subclass to allow arbitrary attribute access. c C s t | �S r( )�bytesr* r$ r$ r% r, ; s z_stdoutBytes.stdoutNr- r$ r$ r$ r% r3 7 s r3 c @ s e Zd ZdZdS )�_AttributeListz/ Like _AttributeString, but for lists. N)r. r/ r0 r1 r$ r$ r$ r% r5 @ s r5 c O s� dd� | D �}|sdS t |�dkr,d}d}nd}d}d tv rHd tj }nd }d ||t|�f }d |v rz|d||d f 7 }d|v r�|d }t|d�s�|g}t |�dkr�d}nd}dd� |D �} |d|t| �f 7 }t|� dS )al Check for given keys in the shared environment dict and abort if not found. Positional arguments should be strings signifying what env vars should be checked for. If any of the given arguments do not exist, Fabric will abort execution and print the names of the missing keys. The optional keyword argument ``used_for`` may be a string, which will be printed in the error output to inform users why this requirement is in place. ``used_for`` is printed as part of a string similar to:: "Th(is|ese) variable(s) (are|is) used for %s" so format it appropriately. The optional keyword argument ``provided_by`` may be a list of functions or function names or a single function or function name which the user should be able to execute in order to set the key or keys; it will be included in the error output if requirements are not met. Note: it is assumed that the keyword arguments apply to all given keys as a group. If you feel the need to specify more than one ``used_for``, for example, you should break your logic into multiple calls to ``require()``. c S s6 g | ].}|t vs.tt | ttttf�rt | s|�qS r$ )r � isinstance�dict�list�tuple�set)�.0�kr$ r$ r% � <listcomp>c s &�zrequire.<locals>.<listcomp>N� zvariables werezThese variables arez variable waszThis variable is�commandz$The command '%s' failed because the zThe z3%sfollowing required environment %s not defined: %sZused_forz %s used for %s� provided_by�__iter__z one of the following commandszthe following commandc S s g | ]}t |d t|���qS )r. )�getattrr) )r; �objr$ r$ r% r= � � z: Try running %s prior to this one, to fix the problem: %s)�lenr r? r �hasattrr ) �keys�kwargsZ missing_keys�variable�used�prefix�msg�funcsr? r@ r$ r$ r% �requireI s< � � �rN � c C s\ t d� |rt�|�}d}|dkr4dt|��� }nd}| �� | }d}|du �r tjdu rjt|�pf|}n t|�pt|}|rHt |�r�z ||�}W nB t y� } z*d}t d� t t |j �d � W Y d}~n d}~0 0 qH|�d �s�d | }|�d �s�|d 7 }t�||�} | sHt d ||f � d}qH|�r,|t|< |�rX|du�rX||k�rXtd |||f � |S ) a� Prompt user with ``text`` and return the input (like ``raw_input``). A single space character will be appended for convenience, but nothing else. Thus, you may want to end your prompt text with a question mark or a colon, e.g. ``prompt("What hostname?")``. If ``key`` is given, the user's input will be stored as ``env.<key>`` in addition to being returned by `prompt`. If the key already existed in ``env``, its value will be overwritten and a warning printed to the user. If ``default`` is given, it is displayed in square brackets and used if the user enters nothing (i.e. presses Enter without entering any text). ``default`` defaults to the empty string. If non-empty, a space will be appended, so that a call such as ``prompt("What hostname?", default="foo")`` would result in a prompt of ``What hostname? [foo]`` (with a trailing space after the ``[foo]``.) The optional keyword argument ``validate`` may be a callable or a string: * If a callable, it is called with the user's input, and should return the value to be stored on success. On failure, it should raise an exception with an exception message, which will be printed to the user. * If a string, the value passed to ``validate`` is used as a regular expression. It is thus recommended to use raw strings in this case. Note that the regular expression, if it is not fully matching (bounded by ``^`` and ``$``) it will be made so. In other words, the input must fully match the regex. Either way, `prompt` will re-prompt until validation passes (or the user hits ``Ctrl-C``). .. note:: `~fabric.operations.prompt` honors :ref:`env.abort_on_prompts <abort-on-prompts>` and will call `~fabric.utils.abort` instead of prompting if that flag is set to ``True``. If you want to block on user input regardless, try wrapping with `~fabric.context_managers.settings`. Examples:: # Simplest form: environment = prompt('Please specify target environment: ') # With default, and storing as env.dish: prompt('Specify favorite dish: ', 'dish', default='spam & eggs') # With validation, i.e. requiring integer input: prompt('Please specify process nice level: ', key='nice', validate=int) # With validation against a regular expression: release = prompt('Please supply a release name', validate=r'^\w+-\d+(\.\d+)?$') # Prompt regardless of the global abort-on-prompts setting: with settings(abort_on_prompts=False): prompt('I seriously need an answer on this! ') z a user-specified prompt() callrO z [%s] � NTz+Validation failed for the following reason:� �^r z?Regular expression validation failed: '%s' does not match '%s' zCoverwrote previous env variable '%s'; used to be '%s', is now '%s'.)r r �getr) �strip�six�PY3�input� raw_input�callable� Exception�printr �message� startswith�endswith�re�findallr ) �text�key�default�validate�previous_valueZ default_strZ prompt_str�value�e�resultr$ r$ r% �prompt� sH < * �ri FTc C sB | p t �� } t| d�o t| j� }ttj�}t|����}|� d�} |pH| }|� d�rb|� d| d�}|du rn| }t j � |�s�t�d�r�tj�d�d | }n t�| |�}|r�t j �| �} t| t�} |r�t| �} q�t j �| �r�| g} q�g } n| g} |�r | �s d| } t| ��|�|��rB|�rBt| �dk�rB|�|��sBtd | ��g } g } | D ]�}zX|�r�t j �|��r�|�||||||�}| �|� n |� |||||||�}| � |� W nR t �y� } z8d }|�r�|nd }| � |� t || |d � W Y d}~n d}~0 0 �qNt | �}| |_!|j! |_"|W d � S 1 �s40 Y dS ) a� Upload one or more files to a remote host. As with the OpenSSH ``sftp`` program, `.put` will overwrite pre-existing remote files without requesting confirmation. `~fabric.operations.put` returns an iterable containing the absolute file paths of all remote files uploaded. This iterable also exhibits a ``.failed`` attribute containing any local file paths which failed to upload (and may thus be used as a boolean test.) You may also check ``.succeeded`` which is equivalent to ``not .failed``. ``local_path`` may be a relative or absolute local file or directory path, and may contain shell-style wildcards, as understood by the Python ``glob`` module (give ``use_glob=False`` to disable this behavior). Tilde expansion (as implemented by ``os.path.expanduser``) is also performed. ``local_path`` may alternately be a file-like object, such as the result of ``open('path')`` or a ``StringIO`` instance. .. note:: In this case, `~fabric.operations.put` will attempt to read the entire contents of the file-like object by rewinding it using ``seek`` (and will use ``tell`` afterwards to preserve the previous file position). ``remote_path`` may also be a relative or absolute location, but applied to the remote host. Relative paths are relative to the remote user's home directory, but tilde expansion (e.g. ``~/.ssh/``) will also be performed if necessary. An empty string, in either path argument, will be replaced by the appropriate end's current working directory. While the SFTP protocol (which `put` uses) has no direct ability to upload files to locations not owned by the connecting user, you may specify ``use_sudo=True`` to work around this. When set, this setting causes `put` to upload the local files to a temporary location on the remote end (defaults to remote user's ``$HOME``; this may be overridden via ``temp_dir``), and then use `sudo` to move them to ``remote_path``. In some use cases, it is desirable to force a newly uploaded file to match the mode of its local counterpart (such as when uploading executable scripts). To do this, specify ``mirror_local_mode=True``. Alternately, you may use the ``mode`` kwarg to specify an exact mode, in the same vein as ``os.chmod``, such as an exact octal number (``0o755``) or a string representing one (``"0o755"``). `~fabric.operations.put` will honor `~fabric.context_managers.cd`, so relative values in ``remote_path`` will be prepended by the current remote working directory, if applicable. Thus, for example, the below snippet would attempt to upload to ``/tmp/files/test.txt`` instead of ``~/files/test.txt``:: with cd('/tmp'): put('/path/to/local/test.txt', 'files') Use of `~fabric.context_managers.lcd` will affect ``local_path`` in the same manner. Examples:: put('bin/project.zip', '/tmp/project.zip') put('*.py', 'cgi-bin/') put('index.html', 'index.html', mode=0o755) .. note:: If a file-like object such as StringIO has a ``name`` attribute, that will be used in Fabric's printed output instead of the default ``<file obj>`` .. versionchanged:: 1.5 Allow a ``name`` attribute on file-like objects for log output .. versionchanged:: 1.7 Added ``use_glob`` option to allow disabling of globbing. �read�.�~r> N�cwd�/z''%s' is not a valid local path or glob.z'%s' is not a directoryz3put() encountered an exception while uploading '%s'z <StringIO>�r\ � exception)#�os�getcwdrF rY rj r r � host_stringr � normalizer] r! �path�isabsrS rm �rstrip� posixpath�join� expanduserr r �exists� ValueErrorrE �isdirZput_dir�extend�put�appendrZ r r5 �failed� succeeded)� local_path� remote_path�use_sudoZmirror_local_mode�modeZuse_glob�temp_dir� local_is_path�ftp�home�names�errZ remote_pathsZfailed_local_pathsZlpath�prg rL Zfailure�retr$ r$ r% r sf Q � � * r c C s, |pd}t |d�ot|j� }|r,t|t�}ttj�}t|����}|�d�}| � d�rd| � d|d�} |rtt j � |�}|du r�|}t j �| �s�t�d�r�tj�d�}|� d d �}|d | } n t�|| �} g }g } z�d | v s�d | v r�|�| �} | s�ttjd ��n| g} |�s:t| �dk�s(|�| d ��r:tdtj| f � | D ]Z} |�| ��rj|�| |||�} |� | � n,|�| |||t j � | �|�} |�r>|� | � �q>W nD t �y� } z*| � | � d} t| | | d� W Y d} ~ n d} ~ 0 0 t |�r�|ng �}| |_!|j! |_"|W d � S 1 �s 0 Y dS )aR Download one or more files from a remote host. `~fabric.operations.get` returns an iterable containing the absolute paths to all local files downloaded, which will be empty if ``local_path`` was a StringIO object (see below for more on using StringIO). This object will also exhibit a ``.failed`` attribute containing any remote file paths which failed to download, and a ``.succeeded`` attribute equivalent to ``not .failed``. ``remote_path`` is the remote file or directory path to download, which may contain shell glob syntax, e.g. ``"/var/log/apache2/*.log"``, and will have tildes replaced by the remote home directory. Relative paths will be considered relative to the remote user's home directory, or the current remote working directory as manipulated by `~fabric.context_managers.cd`. If the remote path points to a directory, that directory will be downloaded recursively. ``local_path`` is the local file path where the downloaded file or files will be stored. If relative, it will honor the local current working directory as manipulated by `~fabric.context_managers.lcd`. It may be interpolated, using standard Python dict-based interpolation, with the following variables: * ``host``: The value of ``env.host_string``, eg ``myhostname`` or ``user@myhostname-222`` (the colon between hostname and port is turned into a dash to maximize filesystem compatibility) * ``dirname``: The directory part of the remote file path, e.g. the ``src/projectname`` in ``src/projectname/utils.py``. * ``basename``: The filename part of the remote file path, e.g. the ``utils.py`` in ``src/projectname/utils.py`` * ``path``: The full remote path, e.g. ``src/projectname/utils.py``. While the SFTP protocol (which `get` uses) has no direct ability to download files from locations not owned by the connecting user, you may specify ``use_sudo=True`` to work around this. When set, this setting allows `get` to copy (using sudo) the remote files to a temporary location on the remote end (defaults to remote user's ``$HOME``; this may be overridden via ``temp_dir``), and then download them to ``local_path``. .. note:: When ``remote_path`` is an absolute directory path, only the inner directories will be recreated locally and passed into the above variables. So for example, ``get('/var/log', '%(path)s')`` would start writing out files like ``apache2/access.log``, ``postgresql/8.4/postgresql.log``, etc, in the local working directory. It would **not** write out e.g. ``var/log/apache2/access.log``. Additionally, when downloading a single file, ``%(dirname)s`` and ``%(path)s`` do not make as much sense and will be empty and equivalent to ``%(basename)s``, respectively. Thus a call like ``get('/var/log/apache2/access.log', '%(path)s')`` will save a local file named ``access.log``, not ``var/log/apache2/access.log``. This behavior is intended to be consistent with the command-line ``scp`` program (but sftp is always used for the transfer). If left blank, ``local_path`` defaults to ``"%(host)s/%(path)s"`` in order to be safe for multi-host invocations. .. warning:: If your ``local_path`` argument does not contain ``%(host)s`` and your `~fabric.operations.get` call runs against multiple hosts, your local files will be overwritten on each successive run! If ``local_path`` does not make use of the above variables (i.e. if it is a simple, explicit file path) it will act similar to ``scp`` or ``cp``, overwriting pre-existing files if necessary, downloading into a directory if given (e.g. ``get('/path/to/remote_file.txt', 'local_directory')`` will create ``local_directory/remote_file.txt``) and so forth. ``local_path`` may alternately be a file-like object, such as the result of ``open('path', 'w')`` or a ``StringIO`` instance. .. note:: Attempting to `get` a directory into a file-like object is not valid and will result in an error. .. note:: This function will use ``seek`` and ``tell`` to overwrite the entire contents of the file-like object, in order to be consistent with the behavior of `~fabric.operations.put` (which also considers the entire file). However, unlike `~fabric.operations.put`, the file pointer will not be restored to its previous location, as that doesn't make as much sense here and/or may not even be possible. .. note:: If a file-like object such as StringIO has a ``name`` attribute, that will be used in Fabric's printed output instead of the default ``<file obj>`` .. versionchanged:: 1.5 Allow a ``name`` attribute on file-like objects for log output z%(host)s/%(path)s�writerk rl r> Nrm rn z\ rP �*�?z No such filer z@[%s] %s is a glob or directory, but local_path is a file object!z5get() encountered an exception while downloading '%s'ro )#rF rY r� r r r rs r rt r] r! rq ru rz rv rS rm rw rx ry r �IOError�errno�ENOENTrE r} r Zget_dirr~ �basenamer� rZ r5 r� r� )r� r� r� r� r� r� r� Zremote_path_escapedZ local_filesZfailed_remote_filesr� rh rg rL r� r$ r$ r% rS � sZ a & rS c C s, |d u r dS t |��� r d| }d| |f S )NrO z#%sz %s "%s")r) �isdigit)�argumentrf r$ r$ r% �_sudo_prefix_argumentQ s r� c C s8 t jt }| dus|dur4d|td| �td|�f S |S )zS Return ``env.sudo_prefix`` with ``user``/``group`` inserted if necessary. Nz%s%s%s z-uz-g)r � sudo_prefixr� )�user�grouprK r$ r$ r% � _sudo_prefixY s �r� c C sX |rt jsd}|du r d}n|d7 }|rHt jd }|r>t| �} d| } nd}|| | S )zN Conditionally wrap given command in env.shell (while honoring sudo.) FNrO rP �"%s")r Z use_shell�shellr& )r? � shell_escaper� r� r$ r$ r% � _shell_wrapf s r� c C sd t tj�}|dkrtjntj}ts&dnd}|rB|�dd||f � d}|rX|�|�| nd}|| S )a� Prefixes ``command`` with all prefixes found in ``env.command_prefixes``. ``env.command_prefixes`` is a list of strings which is modified by the `~fabric.context_managers.prefix` context manager. This function also handles a special-case prefix, ``cwd``, used by `~fabric.context_managers.cd`. The ``which`` kwarg should be a string, ``"local"`` or ``"remote"``, which will determine whether ``cwd`` or ``lcwd`` is used. �remotez >/dev/nullrO r zcd %s%sz && )r8 r Zcommand_prefixesrm Zlcwdr �insertry )r? �which�prefixesrm �redirectZgluerK r$ r$ r% �_prefix_commands� s r� c s� i }t j}|rPt jdkr"d| }n&t jdkr6d| }nt jdkrHd| }||d< |�t j� |r�d\� }trv|rvd � nd }d �� fd d �t�|�D ��}d||f }nd}|| S )av Prefixes ``command`` with any shell environment vars, e.g. ``PATH=foo ``. Currently, this only applies the PATH updating implemented in `~fabric.context_managers.path` and environment variables from `~fabric.context_managers.shell_env`. Will switch to using Windows style 'SET' commands when invoked by ``local()`` and on a Windows localhost. r� z $PATH:"%s"�prependz "%s":$PATHr! r� �PATH)rO rO zSET zexport rP c 3 s0 | ](\}}d � ||dkr |nt |�f V qdS )z %s%s="%s"r� N)r& )r; r< �v�Zset_cmdr$ r% � <genexpr>� s �z#_prefix_env_vars.<locals>.<genexpr>z%s%s && rO ) r ru Z path_behavior�updateZ shell_envr ry rU � iteritems)r? �localZenv_varsru Zexp_cmd�exportsZ shell_env_strr$ r� r% �_prefix_env_vars� s, �r� c C s� |pt j}|pt j}|p t j}|du r,tjn|}|pF|oFtjoF|t ju } tj} | du rZ|} | rf| sfd} t|��� |du r�tj }| � |� | r�t � \} } | j | | d� t � �dd��� dk}d}tjs�|r�tj�| �}|r�| �� |r�| �|d � n | j|d� t| d �}t| d �}|�r$d }}td t| d |||d �td t| d|||d �tdt| || �f}| �� �rn�q�n|D ]}|� � �qrzt � tj � W n& t �y� | �s�� | �!d� Y n0 �q^| �"� }|D ]}|j#�$� |� � �q�| �%� |du�r�|�%� |�s d�$|��&� }d�$|��&� }t'j(�rBt'j�rB|�rB|�)d��r\t'j�rd|�rd|�)d��sdt*d� |||fW d � S 1 �s�0 Y dS )a� Execute ``command`` over ``channel``. ``pty`` controls whether a pseudo-terminal is created. ``combine_stderr`` controls whether we call ``channel.set_combine_stderr``. By default, the global setting for this behavior (:ref:`env.combine_stderr <combine-stderr>`) is consulted, but you may specify ``True`` or ``False`` here to override it. ``invoke_shell`` controls whether we use ``exec_command`` or ``invoke_shell`` (plus a handful of other things, such as always forcing a pty.) ``capture_buffer_size`` controls the length of the ring-buffers used to capture stdout/stderr. (This is ignored if ``invoke_shell=True``, since that completely disables capturing overall.) Returns a three-tuple of (``stdout``, ``stderr``, ``status``), where ``stdout``/``stderr`` are captured output strings and ``status`` is the program's return code, if applicable. NF)�width�heightZ forwardagent�no�yesrQ �r? )�maxlen�out�recv)�capture�stream�timeoutr� Z recv_stderr�in�rO )+�sys�stdinr, �stderrr Zcommand_timeoutZalways_use_pty�remote_interruptr �combine_stderrZset_combine_stderrr Zget_ptyr rS �lowerZ forward_agentr ZagentZAgentRequestHandler� invoke_shell�sendallZ exec_commandr r r r Zexit_status_readyZraise_if_needed�time�sleepZio_sleep�KeyboardInterrupt�sendZrecv_exit_status�threadry �closerT r �runningr^ r[ )�channelr? �ptyr� r� r� r, r� r� �capture_buffer_sizeZ using_ptyr� �rows�colsZ config_agent�forwardZ stdout_bufZ stderr_buf�workersZworker�statusr$ r$ r% �_execute� s� � �� ������r� c C s t t� | dddd� dS )a Invoke a fully interactive shell on the remote end. If ``command`` is given, it will be sent down the pipe before handing control over to the invoking user. This function is most useful for when you need to interact with a heavily shell-based command or series of commands, such as when debugging or when fully interactive recovery is required upon remote program failure. It should be considered an easy way to work an interactive shell session into the middle of a Fabric script and is *not* a drop-in replacement for `~fabric.operations.run`, which is also capable of interacting with the remote end (albeit only while its given command is executing) and has much stronger programmatic abilities such as error handling and stdout/stderr capture. Specifically, `~fabric.operations.open_shell` provides a better interactive experience than `~fabric.operations.run`, but use of a full remote shell prevents Fabric from determining whether programs run within the shell have failed, and pollutes the stdout/stderr stream with shell output such as login banners, prompts and echoed stdin. Thus, this function does not have a return value and will not trigger Fabric's failure handling if any remote programs result in errors. T)r� r? r� r� r� N)r� r r� r$ r$ r% � open_shellN s �r� c c s d V d S r( r$ r$ r$ r$ r% �_noopn s r� c C sp t }|r t}|rt}|� ��> | }| du r6t�dd�} ttt| d��| ||rVt|| �nd�}|rddnd}t j r�t dtj ||f � nt j r�t dtj ||f � tt� |||d|| | | |d � \}}}t|�}|}d|_||_||_|tjv�r2d|_d ||f }tj�r|d | 7 }n|d ||f 7 }t|||d � ||_|j |_||_|W d � S 1 �sb0 Y dS )zP Underpinnings of `run` and `sudo`. See their docstrings for more info. Nr� Tr� �sudo�runz [%s] %s: %sF) r� r? r� r� r� r� r, r� r� r� z4%s() received nonzero return code %s while executingz '%s'!z ! Requested: %s Executed: %s�r\ r, r� )r� �warn_only_manager� quiet_managerr rS r� r� r� r� r �debugr[ rs r� r� r r' r� r? � real_command� ok_ret_codesr r � return_coder� r� )r? r� r� r� r� r� r r r� r, r� r� r� r� r� �manager� given_command�wrapped_commandr� Z result_stdoutZ result_stderrr� r� r� rL r$ r$ r% � _run_commands s\ � � �� r� c C s t | ||||||||| | | d� S )a Run a shell command on a remote host. If ``shell`` is True (the default), `run` will execute the given command string via a shell interpreter, the value of which may be controlled by setting ``env.shell`` (defaulting to something similar to ``/bin/bash -l -c "<command>"``.) Any double-quote (``"``) or dollar-sign (``$``) characters in ``command`` will be automatically escaped when ``shell`` is True (unless disabled by setting ``shell_escape=False``). When ``shell=False``, no shell wrapping or escaping will occur. (It's possible to specify ``shell=False, shell_escape=True`` if desired, which will still trigger escaping of dollar signs, etc but will not wrap with a shell program invocation). `run` will return the result of the remote program's stdout as a single (likely multiline) string. This string will exhibit ``failed`` and ``succeeded`` boolean attributes specifying whether the command failed or succeeded, and will also include the return code as the ``return_code`` attribute. Furthermore, it includes a copy of the requested & actual command strings executed, as ``.command`` and ``.real_command``, respectively. To lessen memory use when running extremely verbose programs (and, naturally, when having access to their full output afterwards is not necessary!) you may limit how much of the program's stdout/err is stored by setting ``capture_buffer_size`` to an integer value. .. warning:: Do not set ``capture_buffer_size`` to any value smaller than the length of ``env.sudo_prompt`` or you will likely break the functionality of `sudo`! Ditto any user prompts stored in ``env.prompts``. .. note:: This value is used for each buffer independently, so e.g. ``1024`` may result in storing a total of ``2048`` bytes if there's data in both streams.) Any text entered in your local terminal will be forwarded to the remote program as it runs, thus allowing you to interact with password or other prompts naturally. For more on how this works, see :doc:`/usage/interactivity`. You may pass ``pty=False`` to forego creation of a pseudo-terminal on the remote end in case the presence of one causes problems for the command in question. However, this will force Fabric itself to echo any and all input you type while the command is running, including sensitive passwords. (With ``pty=True``, the remote pseudo-terminal will echo for you, and will intelligently handle password-style prompts.) See :ref:`pseudottys` for details. Similarly, if you need to programmatically examine the stderr stream of the remote program (exhibited as the ``stderr`` attribute on this function's return value), you may set ``combine_stderr=False``. Doing so has a high chance of causing garbled output to appear on your terminal (though the resulting strings returned by `~fabric.operations.run` will be properly separated). For more info, please read :ref:`combine_streams`. To ignore non-zero return codes, specify ``warn_only=True``. To both ignore non-zero return codes *and* force a command to run silently, specify ``quiet=True``. To override which local streams are used to display remote stdout and/or stderr, specify ``stdout`` or ``stderr``. (By default, the regular ``sys.stdout`` and ``sys.stderr`` Python stream objects are used.) For example, ``run("command", stderr=sys.stdout)`` would print the remote standard error to the local standard out, while preserving it as its own distinct attribute on the return value (as per above.) Alternately, you could even provide your own stream objects or loggers, e.g. ``myout = StringIO(); run("command", stdout=myout)``. If you want an exception raised when the remote program takes too long to run, specify ``timeout=N`` where ``N`` is an integer number of seconds, after which to time out. This will cause ``run`` to raise a `~fabric.exceptions.CommandTimeout` exception. If you want to disable Fabric's automatic attempts at escaping quotes, dollar signs etc., specify ``shell_escape=False``. Examples:: run("ls /var/www/") run("ls /home/myuser", shell=False) output = run('ls /var/www/site1') run("take_a_long_time", timeout=5) .. versionadded:: 1.5 The ``quiet``, ``warn_only``, ``stdout`` and ``stderr`` kwargs. .. versionadded:: 1.5 The return value attributes ``.command`` and ``.real_command``. .. versionadded:: 1.6 The ``timeout`` argument. .. versionadded:: 1.7 The ``shell_escape`` argument. .. versionadded:: 1.11 The ``capture_buffer_size`` argument. .. versionadded:: 1.17 The ``stdin`` argument. )r r r� r, r� r� r� r� )r� ) r? r� r� r� r r r� r, r� r� r� r� r$ r$ r% r� � s m �r� c C s0 t | |||d|r|ntj| ||||| | | | d�S )aR Run a shell command on a remote host, with superuser privileges. `sudo` is identical in every way to `run`, except that it will always wrap the given ``command`` in a call to the ``sudo`` program to provide superuser privileges. `sudo` accepts additional ``user`` and ``group`` arguments, which are passed to ``sudo`` and allow you to run as some user and/or group other than root. On most systems, the ``sudo`` program can take a string username/group or an integer userid/groupid (uid/gid); ``user`` and ``group`` may likewise be strings or integers. You may set :ref:`env.sudo_user <sudo_user>` at module level or via `~fabric.context_managers.settings` if you want multiple ``sudo`` calls to have the same ``user`` value. An explicit ``user`` argument will, of course, override this global setting. Examples:: sudo("~/install_script.py") sudo("mkdir /var/www/new_docroot", user="www-data") sudo("ls /home/jdoe", user=1001) result = sudo("ls /tmp/") with settings(sudo_user='mysql'): sudo("whoami") # prints 'mysql' .. versionchanged:: 1.5 Now honors :ref:`env.sudo_user <sudo_user>`. .. versionadded:: 1.5 The ``quiet``, ``warn_only``, ``stdout`` and ``stderr`` kwargs. .. versionadded:: 1.5 The return value attributes ``.command`` and ``.real_command``. .. versionadded:: 1.7 The ``shell_escape`` argument. .. versionadded:: 1.11 The ``capture_buffer_size`` argument. .. versionadded:: 1.17 The ``stdin`` argument. T) r� r� r� r r r� r, r� r� r� r� )r� r Z sudo_user)r? r� r� r� r� r r r� r, r� r� r� r� r� r$ r$ r% r� 3 s 1 �r� �utf-8c C s | }t | dd�}t|d�}tjr.td| � ntjr@td| � d}|rRd} d} n tj} tj } |rptj} tj} n(t tj d�}tj r�dn|} tj r�dn|} zJtr�|n|g} tj| d| | | | |t d�}|�� \}}W |dur�|�� n|dur�|�� 0 tj�rX|d k�r"t|�pd �}|�p d }n4t|�r8|�|��� nd �}|�rR|�|��� nd }n(t|�rh|�� nd �}|�r||�� nd }||_||_d |_|j|_ ||_ |jt j v�rd|_d |j| f }t |�r�ddgng � � t |||d� W d � n1 �s�0 Y |j |_!|S )a� Run a command on the local system. `local` is simply a convenience wrapper around the use of the builtin Python ``subprocess`` module with ``shell=True`` activated. If you need to do anything special, consider using the ``subprocess`` module directly. ``shell`` is passed directly to `subprocess.Popen <http://docs.python.org/library/subprocess.html#subprocess.Popen>`_'s ``execute`` argument (which determines the local shell to use.) As per the linked documentation, on Unix the default behavior is to use ``/bin/sh``, so this option is useful for setting that value to e.g. ``/bin/bash``. If ``pty`` is changed to ``False``, it redirects the subprocess stdin to an empty pipe to avoid it reading from the terminal, and creates a new "session id" for the subprocess. `local` is not currently capable of simultaneously printing and capturing output, as `~fabric.operations.run`/`~fabric.operations.sudo` do. The ``capture`` kwarg allows you to switch between printing and capturing as necessary, and defaults to ``False``. When ``capture=False``, the local subprocess' stdout and stderr streams are hooked up directly to your terminal, though you may use the global :doc:`output controls </usage/output_controls>` ``output.stdout`` and ``output.stderr`` to hide one or both if desired. In this mode, the return value's stdout/stderr values are always empty. When ``capture=True``, you will not see any output from the subprocess in your terminal, but the return value will contain the captured stdout/stderr. ``encoding`` is used when ``capture=True`` and running under Python-3, to decode stdout and stderr. The default is "utf-8". The special value "binary" avoids decoding, leaving stdout and stderr as ``bytes``. In either case, as with `~fabric.operations.run` and `~fabric.operations.sudo`, this return value exhibits the ``return_code``, ``stderr``, ``failed``, ``succeeded``, ``command`` and ``real_command`` attributes. See `run` for details. `~fabric.operations.local` will honor the `~fabric.context_managers.lcd` context manager, allowing you to control its current working directory independently of the remote end (which honors `~fabric.context_managers.cd`). .. versionadded:: 1.9 The return value attributes ``.command`` and ``.real_command``. .. versionadded:: 1.15 The ``pty`` argument. .. versionadded:: 1.19 The ``encoding`` argument. T)r� r� z[localhost] local: %sz[localhost] local: Nzw+)r� r� r, r� � preexec_fn� executable� close_fds�binaryrD rO FzBlocal() encountered an error (return code %s) while executing '%s'r, r� r� )"r� r� r r� r[ r� � subprocess�PIPErq �setsid�open�devnullr, r� r �Popen� communicater� rU rV r3 r' �decoderT r? r� r� � returncoder� r r� r r r� )r? r� r� r� �encodingr� Zwith_envr� Zdev_nullZ in_streamZpreexecZ out_streamZ err_streamZcmd_argr� r, r� r� r� rL r$ r$ r% r� n sd 8 � � . r� �x �rebootc C sx d}t tt| �t|� ��}ttd�||d��6 |r8tnt|� t�d� t � t j � W d � n1 sj0 Y dS )a\ Reboot the remote system. Will temporarily tweak Fabric's reconnection settings (:ref:`timeout` and :ref:`connection-attempts`) to ensure that reconnection does not give up for at least ``wait`` seconds. .. note:: Users who want greater control are encouraged to check out this function's (6 lines long, well commented) source code and write their own adaptation using different timeout/attempt values or additional logic. .. versionchanged:: 1.4 Changed the ``wait`` kwarg to be optional, and refactored to leverage the new reconnection functionality; it may not actually have to wait for ``wait`` seconds before reconnecting. .. versionchanged:: 1.11 Added ``use_sudo`` as a kwarg. Maintained old functionality by setting the default value to True. � r� )r� Zconnection_attemptsN) �int�round�floatr r r� r� r� r� r �connectr rs )�waitr? r� r� Zattemptsr$ r$ r% r� � s � )NrO N)NNFFNTN)NFN)N)TN)F)TNFNNNNN)N)TTTFNFFNNNNNNN) TTNFFNNNNNN) TTNNFFNNNNNNN)FNTr� )r� r� T)Ir1 r� rq �os.pathrx r_ rU r� r� r� r � collectionsr � contextlibr r Zfabric.context_managersr r r r r� r r� Z fabric.ior r Zfabric.networkr r r Z fabric.sftpr Z fabric.stater r r r r Zfabric.thread_handlingr Z fabric.utilsr r r r r r r r& r) r' r4 r3 r8 r5 rN ri r rS r� r� r� r� r� r� r� r� r� r� r� r� r� r$ r$ r$ r% �<module> s� $ C w � ! - . � � L � s � : {
| ver. 1.1 | |
.
| PHP 8.3.30 | Ð“ÐµÐ½ÐµÑ€Ð°Ñ†Ð¸Ñ Ñтраницы: 0 |
proxy
|
phpinfo
|
ÐаÑтройка