RE: Caches, caches...

Jaap Vermeulen (jaap@sequent.com)
Wed, 16 Mar 94 08:03:00 PST

| 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.

Why not try another directory instead? Like /usr/tmp or whatever. I always
thought it was a weak point that you either have to precompile every and
each module or have write permissions to the library directory. It would be
nice if there were a cache directory for this purpose that can be made
writable for anybody (a la /usr/tmp), although you would have to introduce
some naming scheme or subdirectory structure to distinguish identically
named modules in different locations.

This brings up another interesting point: are the .pyc files guarded against
concurrent generation?

| 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?

If you really want this, I would see it more as a debugging aid for the
programmer/sysadmin and disable it by default and enable it by, say, a
variable in sys or a command line option. :-)

-Jaap-