Martin v. Löwis wrote:
> I think struct compiling should carry the file name, starting in
> PyAST_FromNode.
Thanks! I was trying to add the filename to node but it required too
many changes. I really wonder why I wasn't touching the compiling struct.
Christian
___
> Should the node structure gain an additional field to drag the filename
> around? Or can we simply life with the fact that the user won't get a
> filename in the deprecation warning?
I think struct compiling should carry the file name, starting in
PyAST_FromNode.
Regards,
Martin
___
Christian Heimes wrote:
> Should the node structure gain an additional field to drag the filename
> around?
Why not?
Early on in the design of the Pyrex compiler, I made the decision
that every parse tree node would contain a source filename and
position, down to character resolution. It's paid o
Christian Heimes schrieb:
> Hello!
>
> I'm having a bit of a trouble getting the deprecation warning for
> backquotes `repr` right. Neither the ast_for_* functions in Python/ast.c
> nor the node structures have access to the filename.
On a related note, every time you start a Python interpreter w
Hello!
I'm having a bit of a trouble getting the deprecation warning for
backquotes `repr` right. Neither the ast_for_* functions in Python/ast.c
nor the node structures have access to the filename.
Should the node structure gain an additional field to drag the filename
around? Or can we simply l
