This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author kristjan.jonsson
Recipients kristjan.jonsson, pitrou, rhettinger, serhiy.storchaka, skrah, vstinner
Date 2013-10-14.11:28:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1381750100.17.0.353169778478.issue19256@psf.upfronthosting.co.za>
In-reply-to
Content
Right, the idea of the version token is to introduce it now, as early as possible, even if it is not needed, for prudence.
For example, if version 5 decides to change the semantics of some of the opcodes, we can then support both kinds, in the future.  Read old files _and_ the new ones.

Despite the fact that we claim that we don't guarantee interoperability, in reality it is very desirable.  During development, for instance. Frozen modules, .pyc files, and all that.
History
Date User Action Args
2013-10-14 11:28:20kristjan.jonssonsetrecipients: + kristjan.jonsson, rhettinger, pitrou, vstinner, skrah, serhiy.storchaka
2013-10-14 11:28:20kristjan.jonssonsetmessageid: <1381750100.17.0.353169778478.issue19256@psf.upfronthosting.co.za>
2013-10-14 11:28:20kristjan.jonssonlinkissue19256 messages
2013-10-14 11:28:20kristjan.jonssoncreate