> But you got me thinking... how far back does this behaviour go? ================================= ==> Release 1.1 (11 Oct 1994) <== =================================
- Passing the interpreter a .pyc file as script argument will execute the code in that file. (On the Mac such files can be double-clicked!) - New module compileall generates .pyc files for all modules in a directory (tree) without also executing them [Notice that "on the Mac" refers to Mac System 7 here] ======================================= ==> Release 1.0.0 (26 January 1994) <== ======================================= * It is now possible to have a .pyc file without a corresponding .py file. (Warning: this may break existing installations if you have an old .pyc file lingering around somewhere on your module search path without a corresponding .py file, when there is a .py file for a module of the same name further down the path -- the new interpreter will find the first .pyc file and complain about it, while the old interpreter would ignore it and use the .py file further down.) Regards, Martin -- http://mail.python.org/mailman/listinfo/python-list
