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 vaultah
Recipients r.david.murray, serhiy.storchaka, vaultah
Date 2014-11-05.06:13:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1415168031.45.0.711261710777.issue22619@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not sure what would be the best way to support negative limit for stack functions. Actually, I think the current behavior is not intuitive. For example we could make positive limit mean the same thing for traceback and stack functions (load N entries, starting from the caller), but in that case the change will inverse the behavior of code that uses stack functions. Since the traceback module is mostly used for printing/formatting the difference won't be crucial.
History
Date User Action Args
2014-11-05 06:13:51vaultahsetrecipients: + vaultah, r.david.murray, serhiy.storchaka
2014-11-05 06:13:51vaultahsetmessageid: <1415168031.45.0.711261710777.issue22619@psf.upfronthosting.co.za>
2014-11-05 06:13:51vaultahlinkissue22619 messages
2014-11-05 06:13:50vaultahcreate