> This would eliminate the read-time race condition but still > potentially allow for a write-time race condition if locking isn't > used. The benefit of this approach is that it is no less clear than > pyc is today and doesn't result in n * versions_of_python pyc files. > There is still the overhead of unmarshaling the file to check for a > code object that matches your version. If unmarshaling the entire file > each time is problematic an on-disk format with a short TOC at the > beginning followed by the marshaled data would likely solve the issue.
This was actually what the first draft proposed. Try specifying it in full detail, and you'll find out that a) it is *really* complicated, and b) locking is really tricky to achieve. Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
