FM / compiler

/usr/lib64/python2.7/compiler

Name	Size	Mode	Actions
ast.py	37508	0644	edit dl rm
ast.pyc	72125	0644	edit dl rm
ast.pyo	72125	0644	edit dl rm
consts.py	468	0644	edit dl rm
consts.pyc	737	0644	edit dl rm
consts.pyo	737	0644	edit dl rm
future.py	1893	0644	edit dl rm
future.pyc	2956	0644	edit dl rm
future.pyo	2956	0644	edit dl rm
misc.py	1794	0644	edit dl rm
misc.pyc	3733	0644	edit dl rm
misc.pyo	3733	0644	edit dl rm
pyassem.py	24268	0644	edit dl rm
pyassem.pyc	25951	0644	edit dl rm
pyassem.pyo	25377	0644	edit dl rm
pycodegen.py	47809	0644	edit dl rm
pycodegen.pyc	56515	0644	edit dl rm
pycodegen.pyo	56071	0644	edit dl rm
symbols.py	14489	0644	edit dl rm
symbols.pyc	17677	0644	edit dl rm
symbols.pyo	17643	0644	edit dl rm
syntax.py	1444	0644	edit dl rm
syntax.pyc	1882	0644	edit dl rm
syntax.pyo	1882	0644	edit dl rm
transformer.py	53116	0644	edit dl rm
transformer.pyc	47645	0644	edit dl rm
transformer.pyo	45830	0644	edit dl rm
visitor.py	3896	0644	edit dl rm
visitor.pyc	4187	0644	edit dl rm
visitor.pyo	4187	0644	edit dl rm
__init__.py	1023	0644	edit dl rm
__init__.pyc	1297	0644	edit dl rm
__init__.pyo	1297	0644	edit dl rm

Edit: /usr/lib64/python2.7/compiler/syntax.py (1444B)

"""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.
"""

from compiler import ast, walk

def check(tree, multi=None):
    v = SyntaxErrorChecker(multi)
    walk(tree, v)
    return v.errors

class SyntaxErrorChecker:
    """A visitor to find syntax errors in the AST."""

def __init__(self, multi=None):
        """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.
        """
        self.multi = multi
        self.errors = 0

def error(self, node, msg):
        self.errors = self.errors + 1
        if self.multi is not None:
            print "%s:%s: %s" % (node.filename, node.lineno, msg)
        else:
            raise SyntaxError, "%s (%s:%s)" % (msg, node.filename, node.lineno)

def visitAssign(self, node):
        # the transformer module handles many of these
        pass
##        for target in node.nodes:
##            if isinstance(target, ast.AssList):
##                if target.lineno is None:
##                    target.lineno = node.lineno
##                self.error(target, "can't assign to list comprehension")

"""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. """ from compiler import ast, walk def check(tree, multi=None): v = SyntaxErrorChecker(multi) walk(tree, v) return v.errors class SyntaxErrorChecker: """A visitor to find syntax errors in the AST.""" def __init__(self, multi=None): """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. """ self.multi = multi self.errors = 0 def error(self, node, msg): self.errors = self.errors + 1 if self.multi is not None: print "%s:%s: %s" % (node.filename, node.lineno, msg) else: raise SyntaxError, "%s (%s:%s)" % (msg, node.filename, node.lineno) def visitAssign(self, node): # the transformer module handles many of these pass ## for target in node.nodes: ## if isinstance(target, ast.AssList): ## if target.lineno is None: ## target.lineno = node.lineno ## self.error(target, "can't assign to list comprehension")