[Python-Dev] should I really have to install Python before I can build it ? (original) (raw)

Fredrik Lundh fredrik at pythonware.com
Mon Dec 12 19:27:51 CET 2005

looks like you need to have a recent Python version installed to be able to build the current trunk:

./Parser/asdl_c.py -h ./Include -c ./Python ./Parser/Python.asdl ./Parser/asdl_c.py:150: SyntaxWarning: local name 'self' in 'sum_with_constructors' shadows use of 'self' as global in nested scope 'emit' def sum_with_constructors(self, sum, name, depth): ./Parser/asdl_c.py:263: SyntaxWarning: local name 'self' in 'emit_function' shadows use of 'self' as global in nested scope 'emit' def emit_function(self, name, ctype, args, attrs, union=1): ./Parser/asdl_c.py:296: SyntaxWarning: local name 'self' in 'emit_body_union' shadows use of 'self' as global in nested scope 'emit' def emit_body_union(self, name, args, attrs): ./Parser/asdl_c.py:305: SyntaxWarning: local name 'self' in 'emit_body_struct' shadows use of 'self' as global in nested scope 'emit' def emit_body_struct(self, name, args, attrs): ./Parser/asdl_c.py:444: SyntaxWarning: local name 'self' in 'visitField' shadows use of 'self' as global in nested scope 'emit' def visitField(self, field, name, depth, product): ./Parser/asdl_c.py:444: SyntaxWarning: local name 'depth' in 'visitField' shadows use of 'depth' as global in nested scope 'emit' def visitField(self, field, name, depth, product): ./Parser/asdl_c.py:605: SyntaxWarning: local name 'self' in 'visitField' shadows use of 'self' as global in nested scope 'emit' def visitField(self, field, name, depth, product): ./Parser/asdl_c.py:605: SyntaxWarning: local name 'depth' in 'visitField' shadows use of 'depth' as global in nested scope 'emit' def visitField(self, field, name, depth, product): Traceback (most recent call last): File "./Parser/asdl_c.py", line 9, in ? import asdl File "./Parser/asdl.py", line 53, in ? class ASDLScanner(spark.GenericScanner, object): NameError: name 'object' is not defined make: *** [Include/Python-ast.h] Error 1

(this machine has Python 2.1)

any reason why the C files are not checked into subversion ?

More information about the Python-Dev mailing list