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 techtonik
Recipients amaury.forgeotdarc, techtonik
Date 2012-06-05.17:46:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1338918361.35.0.162083341204.issue15005@psf.upfronthosting.co.za>
In-reply-to
Content
Is it possible to pause trace and resume after the exec call? Between some missing instructions from subprocess internals and traceability of the Python programs I'd choose the latter.

It can be even more actual for people tracing program execution in the process of porting to Python 3.
History
Date User Action Args
2012-06-05 17:46:01techtoniksetrecipients: + techtonik, amaury.forgeotdarc
2012-06-05 17:46:01techtoniksetmessageid: <1338918361.35.0.162083341204.issue15005@psf.upfronthosting.co.za>
2012-06-05 17:46:00techtoniklinkissue15005 messages
2012-06-05 17:46:00techtonikcreate