⚝
One Hat Cyber Team
⚝
Your IP:
216.73.216.30
Server IP:
45.79.8.107
Server:
Linux localhost 5.15.0-140-generic #150-Ubuntu SMP Sat Apr 12 06:00:09 UTC 2025 x86_64
Server Software:
nginx/1.18.0
PHP Version:
8.1.2-1ubuntu2.21
Buat File
|
Buat Folder
Eksekusi
Dir :
~
/
lib
/
python3.10
/
distutils
/
__pycache__
/
View File Name :
core.cpython-310.pyc
o bc" @ 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_namescript r %/usr/lib/python3.10/distutils/core.py gen_usage s r ) distclassr script_argsoptionsnameversionauthor author_email maintainermaintainer_emailurllicense descriptionlong_descriptionkeywords platforms classifiers download_urlrequiresprovides obsoletes)r sources include_dirs define_macros undef_macros library_dirs librariesruntime_library_dirs extra_objectsextra_compile_argsextra_link_args swig_optsexport_symbolsdependslanguagec K s | d}|r | d= nt}d| vr tjtjd | d< d| vr)tjdd | d< z|| a}W n tyQ } zd| vrCt d| t d | d |f d}~ww t d krX|S | t rft d | t d krl|S z| }W n ty } z t t|jd | d}~ww t rt d | t dkr|S |rz| W |S ty t d ty } zt rtjd|f t d|f d}~w ttfy } z t r t dt| d}~ww |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): commandline interruptedz error: %s z error: %szerror: )getr r r r sysargv_setup_distributionDistutilsSetupError SystemExit_setup_stop_afterparse_config_filesr printdump_option_dictsparse_command_lineDistutilsArgErrorr r run_commandsKeyboardInterruptOSErrorstderrwriteDistutilsErrorCCompilerErrorstr)attrsklassdistmsgokexcr r r setup9 st % rS runc C s |dvr t d|f |atj }d| i}z<z3| tjd< |dur(|tjdd< t| d}t| | W d n1 s?w Y W |t_dan|t_daw W n ty[ Y nw t du rft 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. )r5 r6 r7 rT z"invalid value for 'stop_after': %r__file__r Nr4 rbzZ'distutils.core.setup()' was never called -- perhaps '%s' is not a Distutils setup script?) ValueErrorr? r: r; copyopenexecreadr> r< RuntimeError)r r stop_after save_argvgfr r r run_setup s4 ra )NrT )__doc__r r: distutils.debugr distutils.errorsdistutils.distr distutils.cmdr distutils.configr distutils.extensionr r r r? r< setup_keywordsextension_keywordsrS ra r r r r <module> s" q