<br><br><div class="gmail_quote">On Mon, Mar 24, 2008 at 2:30 AM, Jean-Paul Calderone <<a href="mailto:exarkun@divmod.com">exarkun@divmod.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Mon, 24 Mar 2008 00:14:13 +0100, "\"Martin v. Löwis\"" <<a href="mailto:martin@v.loewis.de">martin@v.loewis.de</a>> wrote:<br>
>> You are still only seeing this as a case of libraries with a small<br>
>> number of people developing them and making regular well defined<br>
>> releases. That is not how the world I am talking about looks.<br>
><br>
>Can you give me examples of such software? Are you perhaps talking<br>
>about closed source software?<br>
<br>
</div>I'm not sure what software he was talking about. I can say that for<br>
the work I do on both Twisted and Divmod software, I'd be quite happy<br>
to see this feature. As either part of a migration path towards 3k<br>
_or_ as a feature entirely on its own merits, this would be very useful<br>
to me.<br>
<br>
I'm a bit curious about why Thomas said this sort of thing results in<br>
fragile code. Twisted has been using __future__ imports for years and<br>
they've never been a problem. Twisted currently supports Python 2.3<br>
through Python 2.5, and the only thing that's really difficult about<br>
that is subtle changes in library behavior, not syntax.<br>
</blockquote><div><br>I wasn't talking about future imports. I was talking about writing Python 2.6 code and expecting it to work *the same way* in 3.0 without modification. It requires all programmers working on the project to have knowledge of how 3.0 and 2.6 differ. *I* can't even look at code and tell you how 2.6 and 3.0 will differ. Since Lennart was talking specifically about projects with a large number of developers, I do not believe this is a safe assumption to make. A simple preprocessor step involving 2to3 requires no such knowledge. Or, alternatively, a preprocessor step involving 3to2, which I think will result in better code. Unfortunately I don't have time to work on either anytime soon.<br>
</div></div><br>-- <br>Thomas Wouters <<a href="mailto:thomas@python.org">thomas@python.org</a>><br><br>Hi! I'm a .signature virus! copy me into your .signature file to help me spread!