➜

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 amaury.forgeotdarc
Recipients Markus.Pröller, amaury.forgeotdarc, benjamin.peterson, georg.brandl, maru, mproeller
Date 2010-08-17.08:01:24
SpamBayes Score 0.0004873527
Marked as misclassified No
Message-id <1282032086.02.0.447241395156.issue5215@psf.upfronthosting.co.za>
In-reply-to
Content 
> 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?
History
Date User Action Args
2010-08-17 08:01:27amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, georg.brandl, benjamin.peterson, mproeller, maru, Markus.Pröller
2010-08-17 08:01:26amaury.forgeotdarcsetmessageid: <1282032086.02.0.447241395156.issue5215@psf.upfronthosting.co.za>
2010-08-17 08:01:24amaury.forgeotdarclinkissue5215 messages
2010-08-17 08:01:24amaury.forgeotdarccreate