[issue4725] reporting file locations in egg (and other package) files

Changes by Martin v. Löwis : -- resolution: -> invalid status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue4725] reporting file locations in egg (and other package) files

Martin v. Löwis added the comment: > A use case here is in a stack trace or a debugger where an error > occured. For example does this come from an egg? And if so, which one? > > Perhaps I have missed something in PEP 302, or perhaps this is defined > elsewhere. Please elucidate. Please under

[issue4725] reporting file locations in egg (and other package) files

rocky bernstein added the comment: > > Martin v. Löwis added the comment: > > If this message is about multiple issues (as the second paragraph > suggests), they should be reported separately. As it stands, this is too > much text for me to consider, and it might be too much for other reader

[issue4725] reporting file locations in egg (and other package) files

Martin v. Löwis added the comment: If this message is about multiple issues (as the second paragraph suggests), they should be reported separately. As it stands, this is too much text for me to consider, and it might be too much for other readers as well. When you split it up, please consider wh

[issue4725] reporting file locations in egg (and other package) files

New submission from rocky bernstein : When listing a traceback or showing stack frames or implementing a debugger (or a tool which wants to track the exact location of the source code), how is one supposed to detect a file located inside an egg or some other archive mechanism? There are a numbe