On Tue, 2007-03-13 at 12:52 -0500, Shaun McCance wrote:
If a program works correctly with Python 2.4, is there
actually a danger of it not working correctly with 2.5?
That sounds broken.
Python 2.4 and 2.5 install in parallel so already-built applications
will not be broken.
But if you choose
On Tue, 2007-03-13 at 14:23 -0500, Shaun McCance wrote:
[snip]
You should always test with your minimum requirements.
[snip]
It's not that simple. Some (fairly minor) changes are needed to make
things build with Python 2.5. We already know that they build with
Python 2.4. They need to build with
On 3/14/07, Murray Cumming [EMAIL PROTECTED] wrote:
On Tue, 2007-03-13 at 12:52 -0500, Shaun McCance wrote:
If a program works correctly with Python 2.4, is there
actually a danger of it not working correctly with 2.5?
That sounds broken.
Python 2.4 and 2.5 install in parallel so
On Qua, 2007-03-14 at 13:18 +0200, Fernando Herrera wrote:
On 3/14/07, Murray Cumming [EMAIL PROTECTED] wrote:
On Tue, 2007-03-13 at 12:52 -0500, Shaun McCance wrote:
If a program works correctly with Python 2.4, is there
actually a danger of it not working correctly with 2.5?
That
On Wed, 2007-03-14 at 09:48 +0100, Murray Cumming wrote:
On Tue, 2007-03-13 at 12:52 -0500, Shaun McCance wrote:
I worry that this move would result in programmers using
2.5-only features. Our intrepid testers wouldn't notice,
because they're building from jhbuild. But we'd create
an
On Wed, 2007-03-14 at 09:50 +0100, Murray Cumming wrote:
On Tue, 2007-03-13 at 14:23 -0500, Shaun McCance wrote:
[snip]
You should always test with your minimum requirements.
[snip]
It's not that simple. Some (fairly minor) changes are needed to make
things build with Python 2.5. We
