On 15 abr, 13:58, Michael Torrie <[EMAIL PROTECTED]> wrote: > > After parsing this thread through a noise filter, it appears the main > concern is not the converting of _python code_ from 2 to 3, but rather > converting extensions written in C, or when python is embedded in a C > program. The APIs have necessarily changed, and this *will* inflict a > certain amount of pain and suffering on the developer, especially if he > needs to maintain code for both python 2 and python 3. However this is > just the way it is. It's a bit like complaining that I have to rewrite > my app with win32 calls and paradigms when I was used to win16. No > conversion will be completely pain free, but this jump is pretty > insignificant compared to others in the industry.
Yes, at the C level you have to either live with a lot of #ifdefs, or maintain two branches. I prefer the second choice (with the help of a good SCM tool) but that's a matter of taste or convenience. -- Gabriel Genellina -- http://mail.python.org/mailman/listinfo/python-list