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

Showing content from https://mail.python.org/pipermail/python-dev/2010-March/098136.html below:

[Python-Dev] __file__ and bytecode-only

• Previous message: [Python-Dev] The fate of Distutils in Python 2.7
• Next message: [Python-Dev] __file__ and bytecode-only
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I understand the need to ship without source -- but why does that
require supporting .pyc (or .pyo) -only?

Couldn't vendors just replace the real .py files with empty files?

Then no one would need the extra stat call, and no one would be bitten
by orphaned .pyc files after a rename.

[Yes, zips could still allow unmatched names; yes, it would be helpful
if a tool were available to sync the last-modification time; yes a
deprecation release should still be needed.]

-jJ

• Previous message: [Python-Dev] The fate of Distutils in Python 2.7
• Next message: [Python-Dev] __file__ and bytecode-only
• 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