Michael Mulich <michael.mul...@gmail.com> added the comment: On Mon, Jul 11, 2011 at 11:43 AM, Éric Araujo <rep...@bugs.python.org> wrote: > What do you mean with context? Wouldn’t all three commands just make install_distinfo generate files in the build dir?
Right, my context comment is invalid. > I think that option 4 is the most inelegant, and would be sad to see it win. Ok... I forgot that we now have this RESOURCES file, which makes leaving out the RECORD file less important, but still invalid based on PEP 376. So if we include the RECORD file (point number 2) without the checksum and size (two columns in the RECORD csv format), we will still be PEP376 valid (maybe?), but the file verification information will be missing. And we don't really want this information because if we edit a file, the checksum and size will be incorrect anyhow. This missing information is not important when using the develop or test commands, because we are running the commands on a trusted local copy. What are the consequences of not writing the checksum or size to the RECORD file? And does that solve the issue? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12279> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
