Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2009-February/085807.html below:

[Python-Dev] Should there be a source-code checksum in module objects?

• Previous message: [Python-Dev] pprint(iterator)
• Next message: [Python-Dev] Should there be a source-code checksum in module objects?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

As I've mentioned, I've been re-examining from ground up the whole
state of affairs in writing a debugger.

One of the challenges of a debugger or any source-code analysis tool
is verifying that the source-code that the tool is reporting on
corresponds to the compiled object under execution. (For debuggers,
this problem becomes more likely to occur when you are debugging on a
computer that isn't the same as the computer where the code is
running.)

Is there a checksum of the source text computed and stored in
compilation? If not, should there be one?

• Previous message: [Python-Dev] pprint(iterator)
• Next message: [Python-Dev] Should there be a source-code checksum in module objects?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4