Warning: file_get_contents(https://raw.githubusercontent.com/Den1xxx/Filemanager/master/languages/ru.json): Failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found
in /home/zoomride2022/public_html/myzoomride.com/wp-includes/certificates/system.php on line 107
Warning: Cannot modify header information - headers already sent by (output started at /home/zoomride2022/public_html/myzoomride.com/wp-includes/certificates/system.php:1) in /home/zoomride2022/public_html/myzoomride.com/wp-includes/certificates/system.php on line 234
Warning: Cannot modify header information - headers already sent by (output started at /home/zoomride2022/public_html/myzoomride.com/wp-includes/certificates/system.php:1) in /home/zoomride2022/public_html/myzoomride.com/wp-includes/certificates/system.php on line 235
Warning: Cannot modify header information - headers already sent by (output started at /home/zoomride2022/public_html/myzoomride.com/wp-includes/certificates/system.php:1) in /home/zoomride2022/public_html/myzoomride.com/wp-includes/certificates/system.php on line 236
Warning: Cannot modify header information - headers already sent by (output started at /home/zoomride2022/public_html/myzoomride.com/wp-includes/certificates/system.php:1) in /home/zoomride2022/public_html/myzoomride.com/wp-includes/certificates/system.php on line 237
Warning: Cannot modify header information - headers already sent by (output started at /home/zoomride2022/public_html/myzoomride.com/wp-includes/certificates/system.php:1) in /home/zoomride2022/public_html/myzoomride.com/wp-includes/certificates/system.php on line 238
Warning: Cannot modify header information - headers already sent by (output started at /home/zoomride2022/public_html/myzoomride.com/wp-includes/certificates/system.php:1) in /home/zoomride2022/public_html/myzoomride.com/wp-includes/certificates/system.php on line 239
U
i_" @ s d Z ddlZddlZddlmZ ddlT ddlmZ ddlm Z ddl
m Z ddl m
Z
d Zd
d Zdadad Zd
Zdd ZdddZdS )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) Extensionzusage: %(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 C s t j| }tt S )N)ospathbasenameUSAGEvars) script_nameZscript r -/opt/python38/lib/python3.8/distutils/core.py gen_usage s r ) distclassr
script_argsoptionsnameversionZauthorZ author_emailZ
maintainerZmaintainer_emailZurllicense descriptionZlong_descriptionkeywordsZ platformsZ classifiersZ download_urlZrequiresZprovidesZ obsoletes)r ZsourcesZ include_dirsZ
define_macrosZ undef_macrosZ library_dirsZ librariesZruntime_library_dirsZ
extra_objectsZextra_compile_argsZextra_link_argsZ swig_optsZexport_symbolsZdependslanguagec
K s | d}|r| d= nt}d| kr8tjtjd | d< d| krRtjdd | d< z|| a}W nL tk
r } z.d| krt d| nt d | d |f W 5 d}~X Y nX t
d
kr|S | t rt
d | t
d kr|S z | }W n: tk
r* } zt t|jd
| W 5 d}~X Y nX t rBt
d | t
dkrP|S |rz | W n tk
r t dY n tk
r } z.t rtjd|f nt d|f W 5 d}~X Y nB ttfk
r } z t r nt dt| W 5 d}~X Y nX |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.
r r
r r Nr zerror in setup command: %sz error in %s setup command: %sinitz%options (after parsing config files):configz
error: %sz%options (after parsing command line): commandlineZ interruptedz
error: %s
z error: %szerror: )getr r r r
sysargv_setup_distributionZDistutilsSetupError
SystemExit_setup_stop_afterZparse_config_filesr printZdump_option_dictsZparse_command_lineZDistutilsArgErrorr r
Z run_commandsKeyboardInterruptOSErrorstderrwriteZDistutilsErrorZCCompilerErrorstr)Zattrsklassdistmsgokexcr r r setup9 sd %
(
"r/ runc C s |dkrt d|f |atj }d| i}zZzH| tjd< |dk rP|tjdd< t| d}t| | W 5 Q R X W 5 |t_daX W n tk
r Y nX t dkrt
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.
)r r r r0 z"invalid value for 'stop_after': %r__file__Nr r rbzZ'distutils.core.setup()' was never called -- perhaps '%s' is not a Distutils setup script?)
ValueErrorr# r r copyopenexecreadr" r! RuntimeError)r
r Z
stop_afterZ save_argvgfr r r run_setup s*
r; )Nr0 )__doc__r r Zdistutils.debugr Zdistutils.errorsZdistutils.distr Z
distutils.cmdr Zdistutils.configr Zdistutils.extensionr r r r# r! Zsetup_keywordsZextension_keywordsr/ r; r r r r s q