Showing content from http://mail.python.org/pipermail/python-dev/attachments/20061205/5f2a9f05/attachment.html below:
<br><br><div><span class="gmail_quote">On 12/5/06, <b class="gmail_sendername"><a href="mailto:skip@pobox.com">skip@pobox.com</a></b> <<a href="mailto:skip@pobox.com">skip@pobox.com</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;">
>>>>> "Martin" == Martin v Löwis <<a href="mailto:martin@v.loewis.de">martin@v.loewis.de</a>> writes:<br><br> Martin> <a href="mailto:skip@pobox.com">skip@pobox.com</a> schrieb:<br> >> >> All in all, I think providing binary compatibility would be feasible,
<br> >> >> and should be attempted. What do you think?<br> >><br> Neal> Let's assume that 2.4 is the first LSB version. The ABI is<br> Neal> different for 2.4 and 2.5. We can't change the ABI for
2.5 since<br> Neal> it's already released and our policy is to keep it constant.<br> >><br> >> It seems that adhering to LSB's constraints is going to create a new set of<br> >> problems for Python development. It's unclear to me what LSB brings to
<br> >> Python other than a bunch of new headaches.<br><br> Martin> I won't try to defend it, but would suggest that an evaluation<br> Martin> is deferred until it is clear what the actual problems are, and
<br> Martin> then to judge whether they are additional problems (or perhaps<br> Martin> just a tightening of procedures which we had been following all<br> Martin> along).<br><br>Taking one example from this thread, Python's bytecode has always been an
<br>internal implementation detail. If I read the thread correctly there is at<br>least a request (if not a requirement) to make it part of an external ABI if<br>Python is to become part of the ABI. That may or may not be a large
<br>technical challenge, but I think it would be a significant philosophical<br>change.</blockquote><div><br>I don't think we are being asked to standardize the bytecode, but that we will accept .pyc files as generated by
2.4 in future interpreters as legitimate. That seems to implicitly require us to standardize the bytecode *and* they .pyc file format.<br></div><br>-Brett<br></div><br>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4