Re: Caches, caches...

jredford@lehman.com
Wed, 16 Mar 94 09:25:10 -0500

>> From: Jack Jansen <Jack.Jansen@cwi.nl>
>> Subject: Caches, caches...
>>
>> Guido and myself were discussing the various cache files that python
>> and it's modules make: .pyc files, .fdc files, etc.
>>
>> When these cached files are not available and cannot be created
>> (because a .py file lives in a directory where you don't have write
>> permission, for instance), life will always be slow, and you'll get no
>> notification of this fact.
>>
>> What would people think of a standard warning (Cannot write compiled
>> file /foo/bar.pyc), which could be disabled by, say, a variable in sys
>> or a command line option?

Aiegh. This would be hideous. Document it bigger. Make big caps in the
installation notes that say "YOUR PYTHON WILL BE MUCH MUCH FASTER IF
YOU CREATE THE .PYC FILES FOR .PY FILES", but do NOT go issuing any
warnings on the fly. The very last thing I need, or you need, to get
python programs accepted by my users is a bunch of warnings that
basically mean nothing, everytime I forget to generate a .pyc file for
something. Users dont like seeing warning messages. Anyone who uses
python to any degree in which they care about speed (not everyone
does) will notice all the .pyc files that start clutting up their
directories, and will get the hint.

If you want python -f unwritable-pyc, to turn this type of thing on,
thats fine. I just dont want to see it as a default.

--
John Redford (AKA GArrow) | 3,600 hours of tape.
jredford@lehman.com       | 5 cans of Scotchguard.