[Python-Dev] Importing .pyc in -O mode and vice versa (original) (raw)
Greg Ewing greg.ewing at canterbury.ac.nz
Wed Nov 8 02:38:02 CET 2006
- Previous message: [Python-Dev] Importing .pyc in -O mode and vice versa
- Next message: [Python-Dev] Importing .pyc in -O mode and vice versa
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Armin Rigo wrote:
It would seem good practice to remove all .pycs after checking out a new version of the source, just in case there are other problems such as mismatched timestamps, which can cause the same trouble.
My two cents is that it would be saner to have two separate concepts: cache files used internally by the interpreter for speed reasons only, and bytecode files that can be shipped and imported.
That's a possibility.
-- Greg
- Previous message: [Python-Dev] Importing .pyc in -O mode and vice versa
- Next message: [Python-Dev] Importing .pyc in -O mode and vice versa
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]