|
Apache/2.2.15 (CentOS) Linux obd60-6c49958d75-2q7cw 5.4.0-174-generic #193-Ubuntu SMP Thu Mar 7 14:29:28 UTC 2024 x86_64 uid=48(apache) gid=48(apache) groups=48(apache) server ip : 172.67.192.52 | your ip : 10.244.126.0 safemode OFF > / usr / lib64 / python2.6 / compiler / |
| Filename | /usr/lib64/python2.6/compiler/syntax.pyc |
| Size | 1.84 kb |
| Permission | rw-r--r-- |
| Owner | apache |
| Create time | 23-Dec-2025 17:41 |
| Last modified | 20-Jun-2019 19:45 |
| Last accessed | 20-Jun-2019 19:45 |
| Actions | edit | rename | delete | download (gzip) |
| View | text | code | image |
Ñò
§ÚêLc @ s? d Z d d k l Z l Z d d � Z d d d � � YZ d S( s8 Check for errs in the AST.
The Python parser does not catch all syntax errors. Others, like
assignments with invalid targets, are caught in the code generation
phase.
The compiler package catches some errors in the transformer module.
But it seems clearer to write checkers that use the AST to detect
errors.
iÿÿÿÿ( t astt walkc C s t | � } t | | � | i S( N( t SyntaxErrorCheckerR t errors( t treet multit v( ( s' /usr/lib64/python2.6/compiler/syntax.pyt check s
R c B s, e Z d Z d d � Z d � Z d � Z RS( s+ A visitor to find syntax errors in the AST.c C s | | _ d | _ d S( s¸ Create new visitor object.
If optional argument multi is not None, then print messages
for each error rather than raising a SyntaxError for the
first.
i N( R R ( t selfR ( ( s' /usr/lib64/python2.6/compiler/syntax.pyt __init__ s c C s\ | i d | _ | i d j o d | i | i | f GHn t d | | i | i f � d S( Ni s %s:%s: %ss
%s (%s:%s)( R R t Nonet filenamet linenot SyntaxError( R t nodet msg( ( s' /usr/lib64/python2.6/compiler/syntax.pyt error s c C s d S( N( ( R R ( ( s' /usr/lib64/python2.6/compiler/syntax.pyt visitAssign' s N( t __name__t
__module__t __doc__R
R R R ( ( ( s' /usr/lib64/python2.6/compiler/syntax.pyR s
N( ( R t compilerR R R
R R ( ( ( s' /usr/lib64/python2.6/compiler/syntax.pyt <module>
s
§ÚêLc @ s? d Z d d k l Z l Z d d � Z d d d � � YZ d S( s8 Check for errs in the AST.
The Python parser does not catch all syntax errors. Others, like
assignments with invalid targets, are caught in the code generation
phase.
The compiler package catches some errors in the transformer module.
But it seems clearer to write checkers that use the AST to detect
errors.
iÿÿÿÿ( t astt walkc C s t | � } t | | � | i S( N( t SyntaxErrorCheckerR t errors( t treet multit v( ( s' /usr/lib64/python2.6/compiler/syntax.pyt check s
R c B s, e Z d Z d d � Z d � Z d � Z RS( s+ A visitor to find syntax errors in the AST.c C s | | _ d | _ d S( s¸ Create new visitor object.
If optional argument multi is not None, then print messages
for each error rather than raising a SyntaxError for the
first.
i N( R R ( t selfR ( ( s' /usr/lib64/python2.6/compiler/syntax.pyt __init__ s c C s\ | i d | _ | i d j o d | i | i | f GHn t d | | i | i f � d S( Ni s %s:%s: %ss
%s (%s:%s)( R R t Nonet filenamet linenot SyntaxError( R t nodet msg( ( s' /usr/lib64/python2.6/compiler/syntax.pyt error s c C s d S( N( ( R R ( ( s' /usr/lib64/python2.6/compiler/syntax.pyt visitAssign' s N( t __name__t
__module__t __doc__R
R R R ( ( ( s' /usr/lib64/python2.6/compiler/syntax.pyR s
N( ( R t compilerR R R
R R ( ( ( s' /usr/lib64/python2.6/compiler/syntax.pyt <module>
s