Message 100628 - Python tracker

➜

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.

In-reply-to
Author	dmascialino
Recipients	dmascialino, jjconti, loewis
Date	2010年03月08日.05:28:56
SpamBayes Score	4.947277e-08
Marked as misclassified	No
Message-id	<1268026140.47.0.774697834811.issue8087@psf.upfronthosting.co.za>

Content
Martin, I am not talking about a loop checking source file changes. I think the check could be done only when the traceback is printed. The function PyErr_Display() calls PyTracBack_Print() and so on until _Py_DisplaySourceLine() is called. The latter reads the source file and prints the line. I don't know which is the best way to know if the source file was updated. But i think that it's possible to check it there. I think this could apply only when using the interactive console.

Content

Martin, I am not talking about a loop checking source file changes.
I think the check could be done only when the traceback is printed.
The function PyErr_Display() calls PyTracBack_Print() and so on until _Py_DisplaySourceLine() is called. The latter reads the source file and prints the line. I don't know which is the best way to know if the source file was updated. But i think that it's possible to check it there.
I think this could apply only when using the interactive console.

History
Date	User	Action	Args
2010年03月08日 05:29:01	dmascialino	set	recipients: + dmascialino, loewis, jjconti
2010年03月08日 05:29:00	dmascialino	set	messageid: <1268026140.47.0.774697834811.issue8087@psf.upfronthosting.co.za>
2010年03月08日 05:28:58	dmascialino	link	issue8087 messages
2010年03月08日 05:28:57	dmascialino	create

homepage