File: //proc/2/cwd/usr/lib64/python2.4/distutils/core.pyo
mς
=5Dc @ s° d Z d Z d k Z d k Z d k Td k l Z d k Td k l Z d k
l Z d k l
Z
d k l Z d Z d
Z d a d a d. Z d/ Z d+ Z d d, d- Z d S(0 s# 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.
s0 $Id: core.py 37828 2004-11-10 22:23:15Z loewis $N( t *( s DEBUG( s grok_environment_error( s Distribution( s Command( s Extensions° 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 C s t i i | } t t S( N( t ost patht basenamet script_namet scriptt USAGEt vars( R R ( ( t& /usr/lib64/python2.4/distutils/core.pyt gen_usage$ s t distclassR t script_argst optionst namet versiont authort author_emailt
maintainert maintainer_emailt urlt licenset descriptiont long_descriptiont keywordst platformst classifierst download_urlt sourcest include_dirst
define_macrost undef_macrost library_dirst librariest runtime_library_dirst
extra_objectst extra_compile_argst extra_link_argst swig_optst export_symbolst dependst languagec K sk | i d } | o | d =n t } | i d p! t i i t i d | d <n | i d p t i d | d <n y | | a
} WnM t j
oA } | i d o t d | d | f qα t d | n Xt d j o | Sn | i t o d
GH| i n t d j o | Sn y | i } Wn/ t j
o# } t t | i d | n Xt o d
GH| i n t d j o | Sn | oΐ y | i Wqgt j
o t d qgt t i f j
o@ } t | } t o t i i | d qct | qgt t! f j
o* } t o qct d t" | qgXn | S( sΜ 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 i R i R
s error in %s setup command: %ss error in setup command: %st inits% options (after parsing config files):t configs
error: %ss% options (after parsing command line):t commandlinet interrupteds
s error: N(# t attrst gett klasst Distributiont has_keyR R R t syst argvt _setup_distributiont distt DistutilsSetupErrort msgt
SystemExitt _setup_stop_aftert parse_config_filest DEBUGt dump_option_dictst parse_command_linet okt DistutilsArgErrorR R t run_commandst KeyboardInterruptt IOErrort errort exct grok_environment_errort stderrt writet DistutilsErrort CCompilerErrort str( R- R5 R7 R> RD R/ RC ( ( R t setup; sb !
t runc C sΣ | d
j o t d | f n | a t i } h } h } yV z? | t i d <| d j o | t i d )n t | | | Wd | t _ d a XWn t j
o n n Xt
d j o t d | n t
S( s) 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 run with 'execfile()';
'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+ RL s" invalid value for 'stop_after': %ri i NsZ 'distutils.core.setup()' was never called -- perhaps '%s' is not a Distutils setup script?( s inits configs commandlineRL ( t
stop_aftert
ValueErrorR9 R2 R3 t save_argvt gt lR R t Nonet execfileR8 R4 t RuntimeError( R R RM RP RO RQ ( ( R t run_setup s0
( s distclasss script_names script_argsR s names versionR R R R R s licenseR R R R R R ( s nameR R R R R R R! R" R# R$ R% R& R' R( ( t __doc__t __revision__R2 R t typest distutils.debugR; t distutils.errorst distutils.utilRE t distutils.distR0 t
distutils.cmdt Commandt distutils.extensiont ExtensionR R RR R9 R4 t setup_keywordst extension_keywordsRK RU ( RU RW Rb R` Ra R2 R RE R R^ R; R0 R RK ( ( R t ? s"
r