Brett Cannon <br...@python.org> added the comment: On Mon, Jan 9, 2012 at 18:05, Antoine Pitrou <rep...@bugs.python.org> wrote:
> > Antoine Pitrou <pit...@free.fr> added the comment: > > > I'm not suggesting two stat calls (in the general case); you would > > call one or the other depending on the magic number of the pyc file. > > The proposal is to store both mtime and size, actually, to make false > positives less likely. Then a method that returns some object representing all of the needed info on the source file is needed, but that does NOT blindly return the stat info (eg. modification date, "file" size, and even source as bytes can be in this object). It could even have methods to generate the bytecode, etc. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13645> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
