Critics have remarked that those four worthies were truly peerless throughout the ages; yet the present falls short of the pastβ€”the ancients favored unadorned simplicity, whereas the moderns prefer refined elegance. Styles of substance and ornament rise and fall in succession, shifting with the changing mores of the times; such evolution is simply the natural order of things. The ideal lies in honoring antiquity without clashing with the present, and embracing modernity without succumbing to its flawsβ€”embodying that perfect balance of substance and refinement that defines the true gentleman. There is surely no need to abandon a carved palace in favor of a cave dwelling, or to trade a jade carriage for a primitive cart with solid wooden wheels.🌌 SpectraShell

🌌 SpectraShell

Current path: lib64/python2.7/



⬆️ Go up: /lib64

πŸ“„ Viewing: codeop.pyc

οΏ½
zfc@sοΏ½dZddlZgejD]ZeeeοΏ½^qZdddgZdZdοΏ½ZdοΏ½Z	d	d
dοΏ½Z
dddοΏ½οΏ½YZddd
οΏ½οΏ½YZdS(s[Utilities to compile possibly incomplete Python source code.

This module provides two interfaces, broadly similar to the builtin
function compile(), which take program text, a filename and a 'mode'
and:

- Return code object if the command is complete and valid
- Return None if the command is incomplete
- Raise SyntaxError, ValueError or OverflowError if the command is a
  syntax error (OverflowError and ValueError can be produced by
  malformed literals).

Approach:

First, check if the source consists entirely of blank lines and
comments; if so, replace it with 'pass', because the built-in
parser doesn't always do the right thing for these.

Compile three times: as is, with \n, and with \n\n appended.  If it
compiles as is, it's complete.  If it compiles with one \n appended,
we expect more.  If it doesn't compile either way, we compare the
error we get when compiling with \n or \n\n appended.  If the errors
are the same, the code is broken.  But if the errors are different, we
expect more.  Not intuitive; not even guaranteed to hold in future
releases; but this matches the compiler's behavior from Python 1.4
through 2.2, at least.

Caveat:

It is possible (but not likely) that the parser stops parsing with a
successful outcome before reaching the end of the source; in this
case, trailing symbols may be ignored instead of causing an error.
For example, a backslash followed by two newlines may be followed by
arbitrary garbage.  This will be fixed once the API for the parser is
better.

The two interfaces are:

compile_command(source, filename, symbol):

    Compiles a single command in the manner described above.

CommandCompiler():

    Instances of this class have __call__ methods identical in
    signature to compile_command; the difference is that if the
    instance compiles program text containing a __future__ statement,
    the instance 'remembers' and compiles all subsequent program texts
    with the statement in force.

The module also provides another class:

Compile():

    Instances of this class act like the built-in function compile,
    but with 'memory' in the sense described above.
iοΏ½οΏ½οΏ½οΏ½Ntcompile_commandtCompiletCommandCompilericCs6xR|jdοΏ½D],}|jοΏ½}|r|ddkrPqqW|dkrUd}nd}}}d}}	}
y||||οΏ½}Wntk
rοΏ½}nXy||d||οΏ½}	Wntk
rοΏ½}nXy||d||οΏ½}
Wntk
rοΏ½}nX|r|S|	r2t|οΏ½t|οΏ½kr2t|οΏ½ndS(Ns
it#tevaltpasss

(tsplittstriptNonetSyntaxErrortrepr(tcompilertsourcetfilenametsymboltlineterrterr1terr2tcodetcode1tcode2((s/usr/lib64/python2.7/codeop.pyt_maybe_compileDs0	cCst|||tοΏ½S(N(tcompiletPyCF_DONT_IMPLY_DEDENT(RR
R((s/usr/lib64/python2.7/codeop.pyt_compileess<input>tsinglecCstt|||οΏ½S(ssCompile a command and determine whether it is incomplete.

    Arguments:

    source -- the source string; may contain \n characters
    filename -- optional filename from which source was read; default
                "<input>"
    symbol -- optional grammar start symbol; "single" (default) or "eval"

    Return value / exceptions raised:

    - Return a code object if the command is complete and valid
    - Return None if the command is incomplete
    - Raise SyntaxError, ValueError or OverflowError if the command is a
      syntax error (OverflowError and ValueError can be produced by
      malformed literals).
    (RR(RR
R((s/usr/lib64/python2.7/codeop.pyRhscBs eZdZdοΏ½ZdοΏ½ZRS(sοΏ½Instances of this class behave much like the built-in compile
    function, but if one is used to compile text containing a future
    statement, it "remembers" and compiles all subsequent program texts
    with the statement in force.cCs
t|_dS(N(Rtflags(tself((s/usr/lib64/python2.7/codeop.pyt__init__οΏ½scCsUt||||jdοΏ½}x3tD]+}|j|j@r"|j|jO_q"q"W|S(Ni(RRt	_featurestco_flagst
compiler_flag(RRR
Rtcodeobtfeature((s/usr/lib64/python2.7/codeop.pyt__call__οΏ½s

(t__name__t
__module__t__doc__RR#(((s/usr/lib64/python2.7/codeop.pyR|s	cBs&eZdZdοΏ½ZdddοΏ½ZRS(s(Instances of this class have __call__ methods identical in
    signature to compile_command; the difference is that if the
    instance compiles program text containing a __future__ statement,
    the instance 'remembers' and compiles all subsequent program texts
    with the statement in force.cCstοΏ½|_dS(N(RR(R((s/usr/lib64/python2.7/codeop.pyRοΏ½ss<input>RcCst|j|||οΏ½S(sοΏ½Compile a command and determine whether it is incomplete.

        Arguments:

        source -- the source string; may contain \n characters
        filename -- optional filename from which source was read;
                    default "<input>"
        symbol -- optional grammar start symbol; "single" (default) or
                  "eval"

        Return value / exceptions raised:

        - Return a code object if the command is complete and valid
        - Return None if the command is incomplete
        - Raise SyntaxError, ValueError or OverflowError if the command is a
          syntax error (OverflowError and ValueError can be produced by
          malformed literals).
        (RR(RRR
R((s/usr/lib64/python2.7/codeop.pyR#οΏ½s(R$R%R&RR#(((s/usr/lib64/python2.7/codeop.pyRοΏ½s	(((
R&t
__future__tall_feature_namestfnametgetattrRt__all__RRRRRR(((s/usr/lib64/python2.7/codeop.pyt<module>9s"	!	


πŸ“