B

r�=I�Q�!�@s�dZd
dl
Z
d
dlZd
dlmZ
d
dlTd
dlmZ
d
dlm	Z	
d
dl
mZ
d
dlm
Z

d	Zd
d�ZdadadZd
Zdd�Zddd�
ZdS)a#
distutils.core

The only module that needs to be imported to use the Distutils; provides
the 'setup' function (which is to be called from the setup script).  Also
indirectly provides the Distribution and Command classes, although they are
really defined in distutils.dist and distutils.cmd.
�N)
�DEBUG)
�
*)
�Distribution)
�Command)
�
PyPIRCCommand)
�	Extensionz�usage: %(script)s [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
   or: %(script)s --help [cmd1 cmd2 ...]
   or: %(script)s --help-commands
   or: %(script)s cmd --help
c
Cstj
�|�
}
tt�S)
N)�os�path�basename�USAGE�vars)�script_nameZscript�r�3/opt/alt/python37/lib64/python3.7/distutils/core.py�	gen_usage s

r)�	distclassr
�script_argsZoptions�name�versionZauthorZauthor_emailZ
maintainerZmaintainer_emailZurl�licenseZdescriptionZlong_description�keywordsZ	platformsZclassifiersZdownload_urlZrequiresZprovidesZ	obsoletes)rZsourcesZinclude_dirsZ
define_macrosZundef_macrosZlibrary_dirsZ	librariesZruntime_library_dirsZ
extra_objectsZextra_compile_argsZextra_link_argsZ	swig_optsZexport_symbolsZdependsZlanguagec
Ks|�d
�
}
|
r|d
=nt
}
d|kr8tj�tjd�
|d<d|krRtjdd�|d<y|
|�
a}WnLtk
r�
}
z.d|kr�t	d|�
�
nt	d	|d|f�
�
Wdd}~XYnXt
d
kr�|S|��
tr�t
d�

|��
t
dkr�|Sy|��}Wn:tk
�
r*
}
zt	t|j�
d
|�
�
Wdd}~XYnXt�
rBt
d�

|��
t
dk�
rP|S|�ry|��
Wn�tk
�
r�


t	d�
�
Yn�tk
�
r�
}
z.t�
r�tj�d|f
�

�nt	d|f
�
�
Wdd}~XYnBttfk
�r
}
zt�
r�nt	dt|�
�
�
Wdd}~XYnX|S)a�The gateway to the Distutils: do everything your setup script needs
    to do, in a highly flexible and user-driven way.  Briefly: create a
    Distribution instance; find and parse config files; parse the command
    line; run each Distutils command found there, customized by the options
    supplied to 'setup()' (as keyword arguments), in config files, and on
    the command line.

    The Distribution instance might be an instance of a class supplied via
    the 'distclass' keyword argument to 'setup'; if no such class is
    supplied, then the Distribution class (in dist.py) is instantiated.
    All other arguments to 'setup' (except for 'cmdclass') are used to set
    attributes of the Distribution instance.

    The 'cmdclass' argument, if supplied, is a dictionary mapping command
    names to command classes.  Each command encountered on the command line
    will be turned into a command class, which is in turn instantiated; any
    class found in 'cmdclass' is used in place of the default, which is
    (for command 'foo_bar') class 'foo_bar' in module
    'distutils.command.foo_bar'.  The command class must provide a
    'user_options' attribute which is a list of option specifiers for
    'distutils.fancy_getopt'.  Any command-line options between the current
    and the next command are used to set attributes of the current command
    object.

    When the entire command-line has been successfully parsed, calls the
    'run()' method on each command object in turn.  This method will be
    driven entirely by the Distribution object (which each command object
    has a reference to, thanks to its constructor), and the
    command-specific options that became attributes of each command
    object.
    rr
r
r�
Nrzerror in setup command: %szerror in %s setup command: %s�initz%options (after parsing config files):�configz

error: %sz%options (after parsing command line):�commandlineZinterruptedz
error: %s
z	error: %szerror: )�getrrr	r
�sys�argv�_setup_distributionZDistutilsSetupError�
SystemExit�_setup_stop_afterZparse_config_filesr�printZdump_option_dictsZparse_command_lineZDistutilsArgErrorrr
Zrun_commands�KeyboardInterrupt�OSError�stderr�writeZDistutilsErrorZCCompilerError�str)Zattrs�klassZdist�msg�ok�excrrr�setup9s`%










"






(














"r+�runc	Cs�|d
krtd|f
�
�
|a
tj��}d|i
}yZzH|tjd<|
dk	rP|
tjdd�<t|d��}t|��|�
WdQRXWd|t_da
XWntk
r�


YnXt	dkr�t
d|�
�
t	S)	a.Run a setup script in a somewhat controlled environment, and
    return the Distribution instance that drives things.  This is useful
    if you need to find out the distribution meta-data (passed as
    keyword args from 'script' to 'setup()', or the contents of the
    config files or command-line.

    'script_name' is a file that will be read and run with 'exec()';
    'sys.argv[0]' will be replaced with 'script' for the duration of the
    call.  'script_args' is a list of strings; if supplied,
    'sys.argv[1:]' will be replaced by 'script_args' for the duration of
    the call.

    'stop_after' tells 'setup()' when to stop processing; possible
    values:
      init
        stop after the Distribution instance has been created and
        populated with the keyword arguments to 'setup()'
      config
        stop after config files have been parsed (and their data
        stored in the Distribution instance)
      commandline
        stop after the command-line ('sys.argv[1:]' or 'script_args')
        have been parsed (and the data stored in the Distribution)
      run [default]
        stop after all commands have been run (the same as if 'setup()'
        had been called in the usual way

    Returns the Distribution instance, which provides all information
    used to drive the Distutils.
    )rrrr,z"invalid value for 'stop_after': %r�__file__r
Nr�rbzZ'distutils.core.setup()' was never called -- perhaps '%s' is not a Distutils setup script?)�
ValueErrorr rr�copy�open�exec�readrr�RuntimeError)r
rZ
stop_afterZ	save_argv�
g�
frrr�	run_setup�s(














r7)Nr,)�__doc__rrZdistutils.debugrZdistutils.errorsZdistutils.distrZ
distutils.cmdrZdistutils.configrZdistutils.extensionrrrr rZsetup_keywordsZextension_keywordsr+r7rrrr�<module>s 





	q