➜

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 belopolsky
Recipients belopolsky, doerwalter, ncoghlan, pitrou, vstinner
Date 2010-11-06.03:03:05
SpamBayes Score 3.9592305e-08
Marked as misclassified No
Message-id <AANLkTim0uAV2bctthcgAJwrv8o=weaBLma_b-JyQTmzq@mail.gmail.com>
In-reply-to <1288982590.85.0.299607092654.issue10329@psf.upfronthosting.co.za>
Content 
On Fri, Nov 5, 2010 at 2:43 PM, Antoine Pitrou <report@bugs.python.org> wrote:
..
> Who are the consumers of the trace files? Is there a formal specification
> or is Python the primary consumer?

The trace files contain annotated python source code.  There is no
formal specification that I am aware of as these files are intended
for human consumption.

..
> Relying on the default encoding is not really a good idea, though. This is good for quick scripts or
> in the rare cases where it is by definition the expected behaviour. But in more elaborate cases you
> certainly want to decide the encoding by yourself.

I agree and the correct encoding seems to be the encoding of the
original source file that trace annotates.
History
Date User Action Args
2010-11-06 03:03:09belopolskysetrecipients: + belopolsky, doerwalter, ncoghlan, pitrou, vstinner
2010-11-06 03:03:06belopolskylinkissue10329 messages
2010-11-06 03:03:05belopolskycreate