Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #10348
| From | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| Subject | Re: Only Bytecode, No .py Files |
| Date | 2011-07-26 17:25 -0400 |
| References | <1311693548.3796.212.camel@ewzdev.atlantic> <CAGGBd_rmMyNdqaokHF5aOtC-YS3xjjW83q1-5dQz=wF31NbNbg@mail.gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.1511.1311715565.1164.python-list@python.org> (permalink) |
On 7/26/2011 3:32 PM, Dan Stromberg wrote: > > Another possibility: You could probably create a bunch of zero-length > .py's that are older than the corresponding .pyc's. > > On Tue, Jul 26, 2011 at 8:19 AM, Eldon Ziegler <eldonz@atlanticdb.com > <mailto:eldonz@atlanticdb.com>> wrote: > > Is there a way to have the Python processor look only for bytecode > files, not .py files? We are seeing huge numbers of Linux audit messages > on production system on which only bytecode files are stored. The audit > subsystem is recording each open failure. Try packaging the app into a zip file so there is only one open, which succeeds. -- Terry Jan Reedy
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Only Bytecode, No .py Files Terry Reedy <tjreedy@udel.edu> - 2011-07-26 17:25 -0400
csiph-web