File: //lib64/python3.6/distutils/__pycache__/errors.cpython-36.opt-1.pyc
3
\ù
ã @ s8 d Z G dd„ deƒZG dd„ deƒZG dd„ deƒZG dd„ deƒZG d d
„ d
eƒZG dd„ deƒZG d
d„ deƒZG dd„ deƒZ G dd„ deƒZ
G dd„ deƒZG dd„ deƒZG dd„ deƒZ
G dd„ deƒZG dd„ deƒZG dd„ deƒZG dd „ d eƒZG d!d"„ d"eƒZG d#d$„ d$eƒZG d%d&„ d&eƒZd'S )(a‹ distutils.errors
Provides exceptions used by the Distutils modules. Note that Distutils
modules may raise standard exceptions; in particular, SystemExit is
usually raised for errors that are obviously the end-user's fault
(eg. bad command-line arguments).
This module is safe to use in "from ... import *" mode; it only exports
symbols whose names start with "Distutils" and end with "Error".c @ s e Zd ZdZdS )ÚDistutilsErrorzThe root of all Distutils evil.N)Ú__name__Ú
__module__Ú__qualname__Ú__doc__© r r ú(/usr/lib64/python3.6/distutils/errors.pyr s r c @ s e Zd ZdZdS )ÚDistutilsModuleErrorz„Unable to load an expected module, or to find an expected class
within some module (in particular, command modules and classes).N)r r r r r r r r r s r c @ s e Zd ZdZdS )ÚDistutilsClassErrorzÝSome command class (or possibly distribution class, if anyone
feels a need to subclass Distribution) is found not to be holding
up its end of the bargain, ie. implementing some part of the
"command "interface.N)r r r r r r r r r s r c @ s e Zd ZdZdS )ÚDistutilsGetoptErrorz7The option table provided to 'fancy_getopt()' is bogus.N)r r r r r r r r r
s r
c @ s e Zd ZdZdS )ÚDistutilsArgErrorzaRaised by fancy_getopt in response to getopt.error -- ie. an
error in the command line usage.N)r r r r r r r r r s r c @ s e Zd ZdZdS )ÚDistutilsFileErrorz“Any problems in the filesystem: expected file not found, etc.
Typically this is for problems that we detect before OSError
could be raised.N)r r r r r r r r r $ s r c @ s e Zd ZdZdS )ÚDistutilsOptionErrora‰ Syntactic/semantic errors in command options, such as use of
mutually conflicting options, or inconsistent options,
badly-spelled values, etc. No distinction is made between option
values originating in the setup script, the command line, config
files, or what-have-you -- but if we *know* something originated in
the setup script, we'll raise DistutilsSetupError instead.N)r r r r r r r r r
* s r
c @ s e Zd ZdZdS )ÚDistutilsSetupErrorzqFor errors that can be definitely blamed on the setup script,
such as invalid keyword arguments to 'setup()'.N)r r r r r r r r r 3 s r c @ s e Zd ZdZdS )ÚDistutilsPlatformErrorzÆWe don't know how to do something on the current platform (but
we do know how to do it on some platform) -- eg. trying to compile
C files on a platform not supported by a CCompiler subclass.N)r r r r r r r r r 8 s r c @ s e Zd ZdZdS )ÚDistutilsExecErrorz`Any problems executing an external program (such as the C
compiler, when compiling C files).N)r r r r r r r r r >