On 3/21/06, <b class="gmail_sendername">Michael P. Soulier</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 21/03/06 Neil Schemenauer said:<br><br>> The other question I haven't seen much discussion about is C API<br>> changes. Are we hoping that people can port extension modules with<br>> little effort or are we going to be doing lots of cleanup?
<br><br>Can the old API stay around for a while? There's little to anger users more<br>than API changes that aren't backwards compatible.<br></blockquote></div><br><br>Python 2.x will be around for a long time and should remain compatible. My view is that Python 3k should be an optional (but hopefully compelling) upgrade and should start afresh without any unnecessary legacy. It sounds like many of the suggested core languages changes for Py3k are likely to be substantial enough to require changes to both Python code and extensions anyway.