OwlCyberSecurity - MANAGER
Edit File: base.cpython-39.pyc
a kH�f�^ � @ s d Z ddlZddlZddlZddlmZmZ ddlmZ ddlm Z ddl Z ddl m Z ddl mZ ddlmZmZ dd lmZmZ d ZG d d � d e�ZG d d� de�ZG dd� de�Zdd� Zdd� ZG dd� de�Z G dd� de �Z G dd� d�Z G dd � d e �Z G d d � d e �Z dS ) z� Base classes for writing management commands (named commands which can be executed through ``django-admin`` or ``manage.py``). � N)�ArgumentParser� HelpFormatter)�partial)� TextIOBase)�checks)�ImproperlyConfigured)� color_style�no_style)�DEFAULT_DB_ALIAS� connections�__all__c s& e Zd ZdZdd�� fdd� Z� ZS )� CommandErrora� Exception class indicating a problem while executing a management command. If this exception is raised during the execution of a management command, it will be caught and turned into a nicely-printed error message to the appropriate output stream (i.e., stderr); as a result, raising this exception (with a sensible description of the error) is the preferred way to indicate that something has gone wrong in the execution of a command. � )� returncodec s || _ t� j|i |�� d S �N)r �super�__init__)�selfr �args�kwargs�� __class__� �]/home/gouroczh/virtualenv/test/3.9/lib/python3.9/site-packages/django/core/management/base.pyr " s zCommandError.__init__)�__name__� __module__� __qualname__�__doc__r � __classcell__r r r r r s r c @ s e Zd ZdZdS )�SystemCheckErrorzC The system check framework detected unrecoverable errors. N)r r r r r r r r r ' s r c sN e Zd ZdZddd�� fdd� Zd � fdd� Z� fdd �Z� fd d �Z� ZS ) � CommandParserz� Customized ArgumentParser class to improve some error messages and prevent SystemExit in several occasions, as SystemExit is unacceptable when a command is called programmatically. N)�missing_args_message�called_from_command_linec s" || _ || _t� jf i |�� d S r )r! r" r r )r r! r" r r r r r 6 s zCommandParser.__init__c s6 | j r(|s(tdd� |D ��s(| �| j � t� �||�S )Nc s s | ]}|� d � V qdS )�-N)� startswith)�.0�argr r r � <genexpr>@ � z+CommandParser.parse_args.<locals>.<genexpr>)r! �any�errorr � parse_args)r r � namespacer r r r+ = s �� zCommandParser.parse_argsc s$ | j rt� �|� n td| ��d S )Nz Error: %s)r" r r* r )r �messager r r r* E s zCommandParser.errorc s> |� dt| ��}t|t�r,t|| jd�|d< t� jf i |��S )N� parser_class)r" )�get�type� issubclassr r r" r �add_subparsers)r r r. r r r r2 K s � z CommandParser.add_subparsers)NN) r r r r r r+ r* r2 r r r r r r / s � r c C s, | j r| j tjd< | jr(tj�d| j� dS )z� Include any default options that all commands should accept here so that ManagementUtility can handle them before searching for user commands. ZDJANGO_SETTINGS_MODULEr N)�settings�os�environ� pythonpath�sys�path�insert)�optionsr r r �handle_default_optionsU s r; c s � fdd�}|S )zEDecorator that forces a command to run with translations deactivated.c sZ ddl m} |�� }|�� z$� | i |��}W |d urV|�|� n|d urT|�|� 0 |S )Nr )� translation)Z django.utilsr< Z get_languageZdeactivate_all�activate)r r r< Z saved_locale�res�� handle_funcr r �wrapperd s � z no_translations.<locals>.wrapperr )r@ rA r r? r �no_translationsa s rB c s< e Zd ZdZh d�Zdd� Z� fdd�Z� fdd�Z� ZS ) �DjangoHelpFormatterz� Customized formatter so that command-specific arguments appear in the --help output before arguments common to all commands. > � --verbosity� --skip-checks� --no-color� --pythonpath� --force-color� --version� --traceback� --settingsc s t |� fdd�d�S )Nc s t | j�� j@ t � kS r )�set�option_strings� show_last)�a�r r r �<lambda>� r( z8DjangoHelpFormatter._reordered_actions.<locals>.<lambda>)�key)�sorted�r �actionsr rP r �_reordered_actions� s �z&DjangoHelpFormatter._reordered_actionsc s& t � j|| �|�g|�R i |�� d S r )r � add_usagerV )r �usagerU r r r r r rW � s z DjangoHelpFormatter.add_usagec s t � �| �|�� d S r )r � add_argumentsrV rT r r r rY � s z!DjangoHelpFormatter.add_arguments) r r r r rN rV rW rY r r r r r rC s s rC c @ sV e Zd ZdZedd� �Zejdd� �Zddd�Zdd � Zd d � Z d d � Z ddd�Z dS )� OutputWrapperz& Wrapper around stdout/stderr c C s | j S r )� _style_funcrP r r r � style_func� s zOutputWrapper.style_funcc C s" |r| � � r|| _n dd� | _d S )Nc S s | S r r ��xr r r rQ � r( z*OutputWrapper.style_func.<locals>.<lambda>)�isattyr[ )r r\ r r r r\ � s � c C s || _ d | _|| _d S r )�_outr\ �ending)r �outrb r r r r � s zOutputWrapper.__init__c C s t | j|�S r )�getattrra )r �namer r r � __getattr__� s zOutputWrapper.__getattr__c C s t | jd�r| j�� d S )N�flush)�hasattrra rg rP r r r rg � s zOutputWrapper.flushc C s t | jd�o| j�� S )Nr_ )rh ra r_ rP r r r r_ � s zOutputWrapper.isatty� Nc C sF |d u r| j n|}|r(|�|�s(||7 }|p0| j}| j�||�� d S r )rb �endswithr\ ra �write)r �msgr\ rb r r r rk � s zOutputWrapper.write)r` )ri NN) r r r r �propertyr\ �setterr rf rg r_ rk r r r r rZ � s rZ c @ s� e Zd ZdZdZdZdZdZdZdZ dZ e � Z d dd �Z d d � Zd d � Zdd� Zdd� Zdd� Zdd� Zdd� Zddddejdfdd�Zdd� Zd d � ZdS ) � BaseCommanda The base class from which all management commands ultimately derive. Use this class if you want access to all of the mechanisms which parse the command-line arguments and work out what code to call in response; if you don't need to change any of that behavior, consider using one of the subclasses defined in this file. If you are interested in overriding/customizing various aspects of the command-parsing and -execution behavior, the normal flow works as follows: 1. ``django-admin`` or ``manage.py`` loads the command class and calls its ``run_from_argv()`` method. 2. The ``run_from_argv()`` method calls ``create_parser()`` to get an ``ArgumentParser`` for the arguments, parses them, performs any environment changes requested by options like ``pythonpath``, and then calls the ``execute()`` method, passing the parsed arguments. 3. The ``execute()`` method attempts to carry out the command by calling the ``handle()`` method with the parsed arguments; any output produced by ``handle()`` will be printed to standard output and, if the command is intended to produce a block of SQL statements, will be wrapped in ``BEGIN`` and ``COMMIT``. 4. If ``handle()`` or ``execute()`` raised any exception (e.g. ``CommandError``), ``run_from_argv()`` will instead print an error message to ``stderr``. Thus, the ``handle()`` method is typically the starting point for subclasses; many built-in commands and command types either place all of their logic in ``handle()``, or perform some additional parsing work in ``handle()`` and then delegate from it to more specialized methods as needed. Several attributes affect behavior at various steps along the way: ``help`` A short description of the command, which will be printed in help messages. ``output_transaction`` A boolean indicating whether the command outputs SQL statements; if ``True``, the output will automatically be wrapped with ``BEGIN;`` and ``COMMIT;``. Default value is ``False``. ``requires_migrations_checks`` A boolean; if ``True``, the command prints a warning if the set of migrations on disk don't match the migrations in the database. ``requires_system_checks`` A list or tuple of tags, e.g. [Tags.staticfiles, Tags.models]. System checks registered in the chosen tags will be checked for errors prior to executing the command. The value '__all__' can be used to specify that all system checks should be performed. Default value is '__all__'. To validate an individual application's models rather than all applications' models, call ``self.check(app_configs)`` from ``handle()``, where ``app_configs`` is the list of application's configuration provided by the app registry. ``stealth_options`` A tuple of any options the command uses which aren't defined by the argument parser. ri Fr )�stderr�stdoutr Nc C sz t |p tj�| _t |ptj�| _|r0|r0td��|r>t� | _nt|�| _| jj| j_ t | j t t f�sv| j tkrvtd��d S )Nz4'no_color' and 'force_color' can't be used together.z/requires_system_checks must be a list or tuple.)rZ r7 rq rp r r �styler �ERRORr\ � isinstance�requires_system_checks�list�tuple� ALL_CHECKS� TypeError)r rq rp �no_color� force_colorr r r r s ��zBaseCommand.__init__c C s t �� S )z� Return the Django version, which should be correct for all built-in Django commands. User-supplied commands can override this method to return their own version. )�django� get_versionrP r r r r} s zBaseCommand.get_versionc K s� |� dt� tf dtj�|�|f | jp*dt| dd�t| dd�d�|��}| j|dd| � � d d � | j|d d d t g d�dd� | j|ddd� | j|ddd� | j|dddd� | j|dddd� | j|d dd d� | j r�|j d dd d� | � |� |S ) z} Create and return the ``ArgumentParser`` which will be used to parse the arguments to this command. �formatter_classz%s %sNr! �_called_from_command_line)�prog� descriptionr! r" rI �versionz'Show program's version number and exit.)�actionr� �helpz-vrD r )r r � � z[Verbosity level; 0=minimal output, 1=normal output, 2=verbose output, 3=very verbose output)�defaultr0 �choicesr� rK z�The Python path to a settings module, e.g. "myproject.settings.main". If this isn't provided, the DJANGO_SETTINGS_MODULE environment variable will be used.)r� rG zMA directory to add to the Python path, e.g. "/home/djangoprojects/myproject".rJ � store_truez!Raise on CommandError exceptions.)r� r� rF z"Don't colorize the command output.rH z)Force colorization of the command output.rE zSkip system checks.)� setdefaultrC r r4 r8 �basenamer� rd �add_base_argumentr} �intru � add_argumentrY )r � prog_name� subcommandr �parserr r r � create_parser& sz ���� � ����� zBaseCommand.create_parserc C s dS )zN Entry point for subclassed commands to add custom arguments. Nr �r r� r r r rY r s zBaseCommand.add_argumentsc O s6 |D ] }|| j v rtj|d< q"q|j|i |�� dS )z� Call the parser's add_argument() method, suppressing the help text according to BaseCommand.suppressed_base_arguments. r� N)�suppressed_base_arguments�argparse�SUPPRESSr� )r r� r r r& r r r r� x s z BaseCommand.add_base_argumentc C s | � ||�}|�� dS )za Print the help message for this command, derived from ``self.usage()``. N)r� � print_help)r r� r� r� r r r r� � s zBaseCommand.print_helpc C s d| _ | �|d |d �}|�|dd� �}t|�}|�dd�}t|� z�z| j|i |�� W nr ty� } zZ|jrv� t |t �r�| j � t |�dd � � n| j � d |jj|f � t�|j� W Y d}~n d}~0 0 W z t�� W n ty� Y n0 n$z t�� W n t�y Y n0 0 dS ) aZ Set up any environment changes requested (e.g., Python path and Django settings), then run this command. If the command raises a ``CommandError``, intercept it and print it sensibly to stderr. If the ``--traceback`` option is present or the raised ``Exception`` is not ``CommandError``, raise it. Tr r r� Nr r c S s | S r r r] r r r rQ � r( z+BaseCommand.run_from_argv.<locals>.<lambda>z%s: %s)r r� r+ �vars�popr; �executer � tracebackrt r rp rk �strr r r7 �exitr r Z close_allr )r �argvr� r: � cmd_optionsr �er r r � run_from_argv� s. $ � zBaseCommand.run_from_argvc O s |d r|d rt d��|d r.tdd�| _n|d rFt� | _d| j_|�d�r^t|d �| _|�d�rvt|d �| _| j r�|d s�| j t kr�| � � n| j | j d � | j r�| � � | j|i |��}|�r| j�r t|�d t� }d | j�|j�� �|| j�|j�� �f }| j�|� |S ) z� Try to execute this command, performing system checks if needed (as controlled by the ``requires_system_checks`` attribute, except if force-skipped). r{ rz z@The --no-color and --force-color options can't be used together.T)r{ Nrq rp Z skip_checks)�tagsZdatabasez%s %s %s)r r rr r rp r\ r/ rZ rq ru rx �check�requires_migrations_checks�check_migrations�handle�output_transactionr r Z SQL_KEYWORD�opsZstart_transaction_sqlZend_transaction_sqlrk )r r r: �output� connectionr r r r� � s< � � zBaseCommand.executec s� t j||||d�}d\}} } d} |r�dd� |D �} dd� |D �} dd� |D �}dd� |D �}d d� |D �}|d f|d f|d f| d f| dfg}|D ]H\}}|r�| t|�7 } �fdd�|D �}d�t|��}| d||f 7 } q�| r�d}|�r,| r�| d7 } | d| dk�rdn| dk�rdnd| t|�| f 7 } t� fdd�|D ���rf�j�d| �| | }t|��n || | }|�r�| �r��j � |dd � � n �j � |� d S ) a Use the system check framework to validate entire Django project. Raise CommandError for any serious message (error or critical errors). If there are only light messages (like warnings), print them to stderr and don't raise an exception. )� app_configsr� �include_deployment_checks� databases)ri ri ri r c S s$ g | ] }|j tjk r|�� s|�qS r )�levelr �INFO� is_silenced�r% r� r r r � <listcomp>� s z%BaseCommand.check.<locals>.<listcomp>c S s6 g | ].}t j|j kr"t jk rn q|�� s|�qS r )r r� r� �WARNINGr� r� r r r r� � s &�c S s6 g | ].}t j|j kr"t jk rn q|�� s|�qS r )r r� r� rs r� r� r r r r� � s &�c S s6 g | ].}t j|j kr"t jk rn q|�� s|�qS r )r rs r� �CRITICALr� r� r r r r� � s &�c S s$ g | ] }t j|jkr|�� s|�qS r )r r� r� r� r� r r r r� s �Z CRITICALSZERRORSZWARNINGSZINFOSZDEBUGSc 3 s6 | ].}|� � r � j�t|��n� j�t|��V qd S r )� is_seriousrr rs r� r� r� rP r r r' s ��z$BaseCommand.check.<locals>.<genexpr>r` z %s: %s z%System check identified some issues: z)System check identified %s (%s silenced).z no issuesr z1 issuez %s issuesc 3 s" | ]}|� � �o|�� V qd S r )r� r� r� )� fail_levelr r r' * r( zSystemCheckError: %sc S s | S r r r] r r r rQ 2 r( z#BaseCommand.check.<locals>.<lambda>N) r Z run_checks�len�joinrS r) rr rs r rp rk rq )r r� r� Zdisplay_num_errorsr� r� r� Z all_issues�header�body�footerZvisible_issue_countZdebugs�infos�warnings�errorsZ criticalsZ sorted_issuesZissues� group_name� formattedrl r )r� r r r� � sv � ������ ��� � zBaseCommand.checkc C s� ddl m} z|tt �}W n ty0 Y dS 0 |�|jj�� �}|r�t dd� |D ��}| j � | j � dt|�d�|�d� �� | j � | j � d �� dS ) zv Print a warning if the set of migrations on disk don't match the migrations in the database. r )�MigrationExecutorNc S s h | ]\}}|j �qS r )� app_label)r% Z migrationZ backwardsr r r � <setcomp>F r( z/BaseCommand.check_migrations.<locals>.<setcomp>z� You have %(unapplied_migration_count)s unapplied migration(s). Your project may not work properly until you apply the migrations for app(s): %(apps_waiting_migration)s.z, )Zunapplied_migration_count�apps_waiting_migrationz-Run 'python manage.py migrate' to apply them.)Z django.db.migrations.executorr� r r r Zmigration_plan�loader�graphZ leaf_nodesrS rq rk rr ZNOTICEr� r� )r r� �executorZplanr� r r r r� 6 s, ����� �z BaseCommand.check_migrationsc O s t d��dS )za The actual logic of the command. Subclasses must implement this method. z8subclasses of BaseCommand must provide a handle() methodN��NotImplementedError)r r r: r r r r� W s �zBaseCommand.handle)NNFF)r r r r r� r r� r� ru Zbase_stealth_optionsZstealth_optionsrL r� r r} r� rY r� r� r� r� r rs r� r� r� r r r r ro � s4 H L $)� `!ro c @ s, e Zd ZdZdZdd� Zdd� Zdd� Zd S ) � AppCommanda A management command which takes one or more installed application labels as arguments, and does something with each of them. Rather than implementing ``handle()``, subclasses must implement ``handle_app_config()``, which will be called once for each application. z%Enter at least one application label.c C s |j ddddd� d S )Nr r� �+z One or more application label.)�metavar�nargsr� )r� r� r r r rY l s �zAppCommand.add_argumentsc s� ddl m� z� fdd�|D �}W n4 ttfyV } ztd| ��W Y d }~n d }~0 0 g }|D ]$}| j|fi |��}|r`|�|� q`d�|�S )Nr ��appsc s g | ]}� � |��qS r )Zget_app_config)r% r� r� r r r� x r( z%AppCommand.handle.<locals>.<listcomp>z8%s. Are you sure your INSTALLED_APPS setting is correct?r` )Z django.appsr� � LookupError� ImportErrorr �handle_app_config�appendr� )r Z app_labelsr: r� r� r� � app_configZ app_outputr r� r r� t s � zAppCommand.handlec K s t d��dS )z� Perform the command's actions for app_config, an AppConfig instance corresponding to an application label given on the command line. zCSubclasses of AppCommand must provide a handle_app_config() method.Nr� )r r� r: r r r r� � s �z AppCommand.handle_app_configN)r r r r r! rY r� r� r r r r r� a s r� c @ s4 e Zd ZdZdZde Zdd� Zdd� Zdd � Zd S ) � LabelCommanda A management command which takes one or more arbitrary arguments (labels) on the command line, and does something with each of them. Rather than implementing ``handle()``, subclasses must implement ``handle_label()``, which will be called once for each label. If the arguments should be names of installed applications, use ``AppCommand`` instead. �labelzEnter at least one %s.c C s |j d| jdd� d S )Nr r� )r� r� )r� r� r� r r r rY � s zLabelCommand.add_argumentsc O s8 g }|D ]$}| j |fi |��}|r|�|� qd�|�S )Nr` )� handle_labelr� r� )r �labelsr: r� r� Z label_outputr r r r� � s zLabelCommand.handlec K s t d��dS )z} Perform the command's actions for ``label``, which will be the string as given on the command line. z?subclasses of LabelCommand must provide a handle_label() methodNr� )r r� r: r r r r� � s �zLabelCommand.handle_labelN) r r r r r� r! rY r� r� r r r r r� � s r� )!r r� r4 r7 r r � functoolsr �ior r| Z django.corer Zdjango.core.exceptionsr Z django.core.management.colorr r Z django.dbr r rx � Exceptionr r r r; rB rC rZ ro r� r� r r r r �<module> s2 & ' --