Eric> Neil Schemenauer <[EMAIL PROTECTED]>:
>> I'm not sure what you mean by "should just work". Source
>> compatibility between 1.5.2 and 2.0 is very high. The 2.0 NEWS file
>> should list all the changes (single argument append and socket
>> addresses are the big ones).
Neil Schemenauer <[EMAIL PROTECTED]>:
> I'm not sure what you mean by "should just work". Source
> compatibility between 1.5.2 and 2.0 is very high. The 2.0 NEWS
> file should list all the changes (single argument append and
> socket addresses are the big ones).
And that change only affected a
On Fri, Feb 09, 2001 at 10:53:53AM -0500, Michael Tiemann wrote:
> OTOH, if somebody can make a really definitive statement that I've
> misinterpreted the responses, and that 2.x _as_ python should just work,
> and if it doesn't, it's a bug that needs to shake out, I can address that
> with our OS
Based on the responses I have seen, it appears that this is not the kind of
issue we want to address in a .1 release. I talked with Matt Wilson, the
most active Python developer here, and he's all for moving to 2.x for our
next .0 product, but for compatibility reasons it sounds like the option of
4 matches
Mail list logo
