Message 127798 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	benjamin.peterson
Recipients	belopolsky, benjamin.peterson
Date	2011-02-03.17:08:02
SpamBayes Score	8.3023544e-08
Marked as misclassified	No
Message-id	<AANLkTikas2vtwjRCKKLzjjjHSL+9KDx_9BYWU6AMvhRJ@mail.gmail.com>
In-reply-to	<1296752433.45.0.101254250853.issue11105@psf.upfronthosting.co.za>

Content
2011/2/3 Alexander Belopolsky <report@bugs.python.org>: > > Alexander Belopolsky <belopolsky@users.sourceforge.net> added the comment: > > Looks like a stack overflow caused by an infinite recursion. I am not sure if it is possible to add cycle detection code without sacrificing performance or setting some arbitrary limits. Yes, it's definitely low priority. It's probably easier to crash the interpreter by producing differently malformed ast anyway. > > I wonder: Why ast nodes need to be mutable? So people can change them.

2011/2/3 Alexander Belopolsky <report@bugs.python.org>:
>
> Alexander Belopolsky <belopolsky@users.sourceforge.net> added the comment:
>
> Looks like a stack overflow caused by an infinite recursion.  I am not sure if it is possible to add cycle detection code without sacrificing performance or setting some arbitrary limits.

Yes, it's definitely low priority. It's probably easier to crash the
interpreter by producing differently malformed ast anyway.

>
> I wonder: Why ast nodes need to be mutable?

So people can change them.

History
Date	User	Action	Args
2011-02-03 17:08:02	benjamin.peterson	set	recipients: + benjamin.peterson, belopolsky
2011-02-03 17:08:02	benjamin.peterson	link	issue11105 messages
2011-02-03 17:08:02	benjamin.peterson	create