Amaury Forgeot d'Arc <amaur...@gmail.com> added the comment:

> In the meantime I have switched to Python 2.6.5,
> but the problem that I described above is still there.
The fix was made for 2.7, and not backported to 2.6.

> Another problem that brought the patch is, that when I move a frame up
> in the stack trace, the variables of the current stack are not available
> any more (only the variables of the newest frame are available).
This is not my experience: the variables of the current frame are available. 
What did you do exactly?

----------
nosy: +amaury.forgeotdarc

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue5215>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to