<br><br><div><span class="gmail_quote">On 12/4/06, <b class="gmail_sendername">"Martin v. Löwis"</b> <<a href="mailto:martin@v.loewis.de">martin@v.loewis.de</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Some people (Robert Schweikert) requested byte-code stability at the<br>LSB meeting: LSB should standardize a certain version of the byte code,<br>and then future versions of Python should continue to support this<br>byte code version.
</blockquote><div><br>Did they say why they wanted to distribute bytecode files? I assume it is either for space considerations or they think it will help to protect their IP somehow.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I explained that this is currently not supported, but would be<br>technically possible; somebody would have to implement it.</blockquote><div><br>I guess we just don't remove opcodes and have import allow bytecode files within a range of magic numbers instead of having to match a specific one.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">What do you think?</blockquote><div><br>I am personally -0. I would prefer not to start supporting people pushing bytecode files around, but I am not going to throw a fit we do end up going down that road.
<br><br>-Brett<br></div><br></div>