Andrea Griffini added the comment:
The error cannot be reproduced on 2.7, 3.3 or 3.4 because the problem has been
fixed with 1e5e497ee33b (issue 17614)
--
nosy: +ag6502
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16547
Andrea Griffini added the comment:
Even porting to the new wonderful 'attr' field is not going to make the code
correct... (the exception could be bubbling up from code down ten frames about
a different unrelated attribute that happens to have the same name in a
different object). BTW cpython
Andrea Griffini added the comment:
I missed all the macrology present :-( ... the following is a patch that takes
it into account (also defines a VISIT_QUIT macro to make more visible the exit
points). The handling has been also extended to visit_stmt because the macros
are shared.
Of course
Andrea Griffini added the comment:
On Mon, Aug 20, 2012 at 12:27 AM, Antoine Pitrou rep...@bugs.python.org wrote:
Indeed I don't like the introduction of COMPILER_STACK_FRAME_SCALE.
Re-using the existing infrastructure would be much easier to maintain.
The default recursion limit is 1000
New submission from Andrea Griffini agr...@tin.it:
This is a fix for issue #5765: stack overflow evaluating eval(() * 3)
The solution was to add two fields (recursion_depth and
recursion_limit) to the symbol table object and just increment and
check the depth in symtable_visit_expr raising
Andrea Griffini agr...@tin.it added the comment:
This is a fix for this issue.
The solution was to add two fields (recursion_depth and
recursion_limit) to the symbol table object and just increment and
check the depth in symtable_visit_expr raising a RuntimeError in case
the limit is exceeded
Andrea Griffini agr...@tin.it added the comment:
I sent an email because I was not able to log in. The patch has been submitted
to the correct issue (6765).
--
resolution: - duplicate
status: open - closed
___
Python tracker rep...@bugs.python.org
Andrea Griffini agr...@tin.it added the comment:
Closing as it was a partial implementation of a bad idea with questionable
gains.
--
resolution: - invalid
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
New submission from Andrea Griffini:
I'm not a user of idle, but when asked about a strange behaviour of the
logging module I digged a bit and found what I think is indeed a problem
in the module itself.
The problem is visible if the module is used from idle (or any other IDE
that keeps the same
