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 benjamin.peterson, serhiy.storchaka
Date 2018-09-08.19:01:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1536433290.4.0.56676864532.issue34588@psf.upfronthosting.co.za>
In-reply-to
Content
It actually does save space because each traceback entry is usually two lines (frame id and source snippet).

I don't really have an opinion about what should happen be printed on the boundary cases. My current PR seems like a strict improvement to the current implementation, which is just incorrect.
History
Date User Action Args
2018-09-08 19:01:30benjamin.petersonsetrecipients: + benjamin.peterson, serhiy.storchaka
2018-09-08 19:01:30benjamin.petersonsetmessageid: <1536433290.4.0.56676864532.issue34588@psf.upfronthosting.co.za>
2018-09-08 19:01:30benjamin.petersonlinkissue34588 messages
2018-09-08 19:01:30benjamin.petersoncreate