Mailing List Archive: Python: Dev

Python 2.6.3

1 2

View All

Index | Next | Previous | View Threaded

barry at python

Sep 9, 2009, 6:01 AM

Post #1 of 36 (2359 views)
Permalink

Python 2.6.3

I had previously wanted to release Python 2.6.3 over the summer, but
for various personal reasons, the summer was just too insane. I'd
like to reschedule a 2.6.3 release, shooting for final release on 25-
September.

We should probably do a release candidate, so I'd like to make that on
23-September.

Does anybody have objections to that schedule? If not, I'll try to
spend some time over the next few days looking at outstanding bugs,
and marking release blockers, etc.

-Barry

Attachments:

PGP.sig (0.81 KB)

ncoghlan at gmail

Sep 9, 2009, 6:29 AM

Post #2 of 36 (2299 views)
Permalink

Re: Python 2.6.3 [In reply to]

Barry Warsaw wrote:
> I had previously wanted to release Python 2.6.3 over the summer, but for
> various personal reasons, the summer was just too insane. I'd like to
> reschedule a 2.6.3 release, shooting for final release on 25-September.
>
> We should probably do a release candidate, so I'd like to make that on
> 23-September.
>
> Does anybody have objections to that schedule? If not, I'll try to
> spend some time over the next few days looking at outstanding bugs, and
> marking release blockers, etc.

2 days seems a little short (particularly allowing 24 hours or so for
the Windows and Mac installers to be produced). Haven't we historically
left a week between the RC and actual release for maintenance releases?

Cheers,
Nick.

--
Nick Coghlan | ncoghlan [at] gmail | Brisbane, Australia
---------------------------------------------------------------
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

barry at python

Sep 9, 2009, 6:52 AM

Post #3 of 36 (2311 views)
Permalink

Re: Python 2.6.3 [In reply to]

On Sep 9, 2009, at 9:29 AM, Nick Coghlan wrote:

> Barry Warsaw wrote:
>> I had previously wanted to release Python 2.6.3 over the summer,
>> but for
>> various personal reasons, the summer was just too insane. I'd like
>> to
>> reschedule a 2.6.3 release, shooting for final release on 25-
>> September.
>>
>> We should probably do a release candidate, so I'd like to make that
>> on
>> 23-September.
>>
>> Does anybody have objections to that schedule? If not, I'll try to
>> spend some time over the next few days looking at outstanding bugs,
>> and
>> marking release blockers, etc.
>
> 2 days seems a little short (particularly allowing 24 hours or so for
> the Windows and Mac installers to be produced). Haven't we
> historically
> left a week between the RC and actual release for maintenance
> releases?

Actually, I've rarely done rc's for point releases. JFDI :)

I still want to release by the 25th, but I'd be willing to move the rc
to Monday the 21st. We're really just trying to avoid a brown bag
moment, so that should give us enough time to double check the releases.

-Barry

Attachments:

PGP.sig (0.81 KB)

nad at acm

Sep 9, 2009, 10:29 AM

Post #4 of 36 (2296 views)
Permalink

Re: Python 2.6.3 [In reply to]

In article <11A6545D-7204-4F61-B55B-1CC77CB5645E [at] python>,
Barry Warsaw <barry [at] python> wrote:
> I still want to release by the 25th, but I'd be willing to move the rc
> to Monday the 21st. We're really just trying to avoid a brown bag
> moment, so that should give us enough time to double check the releases.

The recent release of OS X 10.6 (Snow Leopard) has triggered a fair
amount of 2.6 bug tracker activity, since 10.6 now includes 2.6 (2.6.1)
and a 64-bit version at that. A number of patches have either just
been checked-in over the past couple of weeks or are getting some
exposure before check-in. Given the timing and the (appropriate)
infrequency of 2.6.x releases, I think it would be unfortunate to push
2.6.3 out the door without ensuring that it works well on 10.6.
Therefore, I propose that 2.6.3 should have 10.6 compatibility as a
"release goal".

Without trying to put Ronald on the spot (too much!), it would be a good
idea to get his assessment where things stand wrt 2.6 on 10.6 before
setting a final release date.

--
Ned Deily,
nad [at] acm

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

ronaldoussoren at mac

Sep 9, 2009, 11:19 AM

Post #5 of 36 (2303 views)
Permalink

Re: Python 2.6.3 [In reply to]

On 9 Sep, 2009, at 19:29, Ned Deily wrote:
>
>
> Without trying to put Ronald on the spot (too much!), it would be a
> good
> idea to get his assessment where things stand wrt 2.6 on 10.6 before
> setting a final release date.

MacOS X 10.6 support should be stable now, except for a critical issue
with IDLE: opening a new window hangs IDLE (issue 6864).

That said, I haven't scanned the issue tracker for more 10.6 related
issues.

BTW. I'm fine with a sept. 25th release, that should give us enough time
to shake out issues with OSX 10.6 support.

Ronald

Attachments:

smime.p7s (2.17 KB)

barry at python

Sep 9, 2009, 12:06 PM

Post #6 of 36 (2291 views)
Permalink

Re: Python 2.6.3 [In reply to]

On Sep 9, 2009, at 1:29 PM, Ned Deily wrote:

> In article <11A6545D-7204-4F61-B55B-1CC77CB5645E [at] python>,
> Barry Warsaw <barry [at] python> wrote:
>> I still want to release by the 25th, but I'd be willing to move the
>> rc
>> to Monday the 21st. We're really just trying to avoid a brown bag
>> moment, so that should give us enough time to double check the
>> releases.
>
> The recent release of OS X 10.6 (Snow Leopard) has triggered a fair
> amount of 2.6 bug tracker activity, since 10.6 now includes 2.6
> (2.6.1)
> and a 64-bit version at that. A number of patches have either just
> been checked-in over the past couple of weeks or are getting some
> exposure before check-in. Given the timing and the (appropriate)
> infrequency of 2.6.x releases, I think it would be unfortunate to push
> 2.6.3 out the door without ensuring that it works well on 10.6.
> Therefore, I propose that 2.6.3 should have 10.6 compatibility as a
> "release goal".
>
> Without trying to put Ronald on the spot (too much!), it would be a
> good
> idea to get his assessment where things stand wrt 2.6 on 10.6 before
> setting a final release date.

I'm hoping that Python won't have any issues building and running on
10.6, but I don't have it yet so I can't personally test it out.

How would you quantify "works well"? Do you have any thoughts on
tests you'd run other than the standard test suite? If 2.6.3 is shown
to pass its test suite on 10.5.x, is that good enough? Are the
specific bug fixes necessary for 10.6?

-Barry

Attachments:

PGP.sig (0.81 KB)

zvezdan at zope

Sep 10, 2009, 5:47 AM

Post #7 of 36 (2269 views)
Permalink

Re: Python 2.6.3 [In reply to]

On Sep 9, 2009, at 2:19 PM, Ronald Oussoren wrote:
> MacOS X 10.6 support should be stable now, except for a critical issue
> with IDLE: opening a new window hangs IDLE (issue 6864).
>
> That said, I haven't scanned the issue tracker for more 10.6 related
> issues.

I just opened issue 6877 and provided a patch that I use for a long
time already. It would be nice to have it in the release though since
other people could benefit from it too.

It resolves a BusError crash when Python readline module is built with
a native Mac OS X editline (emulates readline). The patch fixes the
issue and enables use of readline module on Mac OS X.

Best regards,

Zvezdan

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

nad at acm

Sep 10, 2009, 9:23 AM

Post #8 of 36 (2262 views)
Permalink

Re: Python 2.6.3 [In reply to]

In article <9D506035-7C2D-4929-A134-E88EEB7B7D9E [at] python>,
Barry Warsaw <barry [at] python> wrote:

> On Sep 9, 2009, at 1:29 PM, Ned Deily wrote:
>
> > In article <11A6545D-7204-4F61-B55B-1CC77CB5645E [at] python>,
> > Barry Warsaw <barry [at] python> wrote:
> >> I still want to release by the 25th, but I'd be willing to move the
> >> rc
> >> to Monday the 21st. We're really just trying to avoid a brown bag
> >> moment, so that should give us enough time to double check the
> >> releases.
> >
> > The recent release of OS X 10.6 (Snow Leopard) has triggered a fair
> > amount of 2.6 bug tracker activity, since 10.6 now includes 2.6
> > (2.6.1)
> > and a 64-bit version at that. A number of patches have either just
> > been checked-in over the past couple of weeks or are getting some
> > exposure before check-in. Given the timing and the (appropriate)
> > infrequency of 2.6.x releases, I think it would be unfortunate to push
> > 2.6.3 out the door without ensuring that it works well on 10.6.
> > Therefore, I propose that 2.6.3 should have 10.6 compatibility as a
> > "release goal".
> >
> > Without trying to put Ronald on the spot (too much!), it would be a
> > good
> > idea to get his assessment where things stand wrt 2.6 on 10.6 before
> > setting a final release date.
>
> I'm hoping that Python won't have any issues building and running on
> 10.6, but I don't have it yet so I can't personally test it out.
>
> How would you quantify "works well"? Do you have any thoughts on
> tests you'd run other than the standard test suite? If 2.6.3 is shown
> to pass its test suite on 10.5.x, is that good enough? Are the
> specific bug fixes necessary for 10.6?

Running the standard test suite on 10.6 and seeing no regressions
compared to the same suite on 10.5.x seems a reasonable necessary
requirement. We have the resources to do that. Beyond that, as Ronald
suggests, I think it important to go through the open issues in the next
couple of days and identify and flag any potential release-blockers
(besides the IDLE problem already mentioned).

One other open issue is 64-bit support in the python.org OS X installer.
There have been discussions and requests in the past and, with Apple
providing 64-bit out of the box in 10.6, it seems like it's time to
provide something on python.org as well. One option: continue to
provide a 32-bit only installer for ppc and i386 for 10.3.9 and beyond
and add a second installer image with 3-way (ppc, i386, x86_64 but no
ppc64) 32/64 for 10.5 and beyond. Ronald, is that your current
thinking?

--
Ned Deily,
nad [at] acm

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

martin at v

Sep 10, 2009, 9:57 AM

Post #9 of 36 (2261 views)
Permalink

Re: Python 2.6.3 [In reply to]

Barry Warsaw schrieb:
> I had previously wanted to release Python 2.6.3 over the summer, but for
> various personal reasons, the summer was just too insane. I'd like to
> reschedule a 2.6.3 release, shooting for final release on 25-September.

I'm travelling that week (as well as the time until then), so I would
prefer to make it a week later.

Regards,
Martin
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

rowen at uw

Sep 10, 2009, 12:55 PM

Post #10 of 36 (2260 views)
Permalink

Re: Python 2.6.3 [In reply to]

In article <C11F8211-8938-4C68-8221-C3C73E8E517B [at] mac>,
Ronald Oussoren <ronaldoussoren [at] mac> wrote:

> On 9 Sep, 2009, at 19:29, Ned Deily wrote:
> >
> >
> > Without trying to put Ronald on the spot (too much!), it would be a
> > good
> > idea to get his assessment where things stand wrt 2.6 on 10.6 before
> > setting a final release date.
>
> MacOS X 10.6 support should be stable now, except for a critical issue
> with IDLE: opening a new window hangs IDLE (issue 6864).
>
> That said, I haven't scanned the issue tracker for more 10.6 related
> issues.
>
> BTW. I'm fine with a sept. 25th release, that should give us enough time
> to shake out issues with OSX 10.6 support.
>
> Ronald---------------------------------------------------------------------

Some or all earlier Mac binaries of Python 2.6 were not compatible with
3rd party Aqua Tcl/Tk (e.g. ActiveState's versions) -- at least on MacOS
X 10.5. I hope that will be fixed with the current release.

-- Russell

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

barry at python

Sep 11, 2009, 8:29 AM

Post #11 of 36 (2244 views)
Permalink

Re: Python 2.6.3 [In reply to]

On Sep 10, 2009, at 12:57 PM, Martin v. L�wis wrote:

> Barry Warsaw schrieb:
>> I had previously wanted to release Python 2.6.3 over the summer,
>> but for
>> various personal reasons, the summer was just too insane. I'd like
>> to
>> reschedule a 2.6.3 release, shooting for final release on 25-
>> September.
>
> I'm travelling that week (as well as the time until then), so I would
> prefer to make it a week later.

Cool, thanks Martin. Let's make it:

2.6.3rc1 on 29-sep
2.6.3 final on 02-oct

That gives us an extra day between rc and final.

-Barry

Attachments:

PGP.sig (0.81 KB)

ronaldoussoren at mac

Sep 15, 2009, 6:53 AM

Post #12 of 36 (2175 views)
Permalink

Re: Python 2.6.3 [In reply to]

On 10 Sep, 2009, at 18:23, Ned Deily wrote:

> In article <9D506035-7C2D-4929-A134-E88EEB7B7D9E [at] python>,
> Barry Warsaw <barry [at] python> wrote:
>
>> On Sep 9, 2009, at 1:29 PM, Ned Deily wrote:
>>
>>> In article <11A6545D-7204-4F61-B55B-1CC77CB5645E [at] python>,
>>> Barry Warsaw <barry [at] python> wrote:
>>>> I still want to release by the 25th, but I'd be willing to move the
>>>> rc
>>>> to Monday the 21st. We're really just trying to avoid a brown bag
>>>> moment, so that should give us enough time to double check the
>>>> releases.
>>>
>>> The recent release of OS X 10.6 (Snow Leopard) has triggered a fair
>>> amount of 2.6 bug tracker activity, since 10.6 now includes 2.6
>>> (2.6.1)
>>> and a 64-bit version at that. A number of patches have either just
>>> been checked-in over the past couple of weeks or are getting some
>>> exposure before check-in. Given the timing and the (appropriate)
>>> infrequency of 2.6.x releases, I think it would be unfortunate to
>>> push
>>> 2.6.3 out the door without ensuring that it works well on 10.6.
>>> Therefore, I propose that 2.6.3 should have 10.6 compatibility as a
>>> "release goal".
>>>
>>> Without trying to put Ronald on the spot (too much!), it would be a
>>> good
>>> idea to get his assessment where things stand wrt 2.6 on 10.6 before
>>> setting a final release date.
>>
>> I'm hoping that Python won't have any issues building and running on
>> 10.6, but I don't have it yet so I can't personally test it out.
>>
>> How would you quantify "works well"? Do you have any thoughts on
>> tests you'd run other than the standard test suite? If 2.6.3 is
>> shown
>> to pass its test suite on 10.5.x, is that good enough? Are the
>> specific bug fixes necessary for 10.6?
>
> Running the standard test suite on 10.6 and seeing no regressions
> compared to the same suite on 10.5.x seems a reasonable necessary
> requirement. We have the resources to do that. Beyond that, as
> Ronald
> suggests, I think it important to go through the open issues in the
> next
> couple of days and identify and flag any potential release-blockers
> (besides the IDLE problem already mentioned).

The IDLE issue is IMHO a release blocker, as is issue 6851.

>
> One other open issue is 64-bit support in the python.org OS X
> installer.
> There have been discussions and requests in the past and, with Apple
> providing 64-bit out of the box in 10.6, it seems like it's time to
> provide something on python.org as well. One option: continue to
> provide a 32-bit only installer for ppc and i386 for 10.3.9 and beyond
> and add a second installer image with 3-way (ppc, i386, x86_64 but no
> ppc64) 32/64 for 10.5 and beyond. Ronald, is that your current
> thinking?

64-bit support can wait until after 2.6.3 is released. I need time to
work out what's needed go create a good installer (and not just
running the current build-installer.py script because that includes to
much for a binary that doesn't run on 10.3.9). That won't happen
before 2.6.3 is released because I'm too thinly stretched even without
working on that.

Ronald

Attachments:

smime.p7s (2.17 KB)

barry at python

Sep 16, 2009, 5:52 AM

Post #13 of 36 (2149 views)
Permalink

Re: Python 2.6.3 [In reply to]

On Sep 15, 2009, at 9:53 AM, Ronald Oussoren wrote:

> The IDLE issue is IMHO a release blocker, as is issue 6851.

So that leaves 4 release blockers for 2.6.3. Three of these are
assigned to Ronald. Ronald are you sure you will have time to fix
these by then? The one I'm still uncertain on is the IDLE hang. If
this only affects OS X 10.6 and there is no progress on it by the time
2.6.3 is otherwise ready, I'm willing to knock this down in severity.

Martin, you have the other showstopper bug for 2.6.3. Do you think
you will be able to fix that one in time?

-Barry

Attachments:

PGP.sig (0.81 KB)

brett at python

Sep 16, 2009, 12:57 PM

Post #14 of 36 (2150 views)
Permalink

Re: Python 2.6.3 [In reply to]

On Wed, Sep 16, 2009 at 05:52, Barry Warsaw <barry [at] python> wrote:
> On Sep 15, 2009, at 9:53 AM, Ronald Oussoren wrote:
>
>> The IDLE issue is IMHO a release blocker, as is issue 6851.
>
> So that leaves 4 release blockers for 2.6.3. Three of these are assigned to
> Ronald. Ronald are you sure you will have time to fix these by then? The
> one I'm still uncertain on is the IDLE hang. If this only affects OS X 10.6
> and there is no progress on it by the time 2.6.3 is otherwise ready, I'm
> willing to knock this down in severity.
>
> Martin, you have the other showstopper bug for 2.6.3. Do you think you will
> be able to fix that one in time?

That issue doesn't require Martin specifically. I just needed to know
if changing the BaseException struct would be bad (Georg answered w/
"yes"). It will probably fall on to me (or Georg if his proposed
solution pans out) to get this fixed.

-Brett
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

ronaldoussoren at mac

Sep 16, 2009, 1:28 PM

Post #15 of 36 (2151 views)
Permalink

Re: Python 2.6.3 [In reply to]

On 16 Sep, 2009, at 14:52, Barry Warsaw wrote:

> On Sep 15, 2009, at 9:53 AM, Ronald Oussoren wrote:
>
>> The IDLE issue is IMHO a release blocker, as is issue 6851.
>
> So that leaves 4 release blockers for 2.6.3. Three of these are
> assigned to Ronald. Ronald are you sure you will have time to fix
> these by then? The one I'm still uncertain on is the IDLE hang. If
> this only affects OS X 10.6 and there is no progress on it by the
> time 2.6.3 is otherwise ready, I'm willing to knock this down in
> severity.

I don't know for sure if I'll be able to fix these issues, I'll
basicly just have time to work on this during the weekend.

* IDLE hang on OSX 10.6: I don't really know where to start looking,
this may have something to do with Tk-Cocoa (which is used on 10.6 and
not on earlier releases). There is a patch for Tk-Cocoa support on the
tracker, but I haven't had time yet to fully test that.

* Compile error for ctypes on 10.6: Should be easy to fix. Apple has
released the sources of the copy of libffi included with 10.6.1, I'll
use that to work on a patch.

* Crash with urllib and threads on OSX 10.6: This probably requires
rewriting some code using ctypes in C. The crash seems to occur when
CoreFoundation tries to initialise itself after being loaded on a
secondairy thread by ctypes. To make matters worse the ctypes type
annotations in urllib are not correct for 64-bit code (but the crash
happens in 32-bit mode as well)

Ronald

Attachments:

smime.p7s (2.17 KB)

tmm at fastmail

Sep 19, 2009, 11:51 AM

Post #16 of 36 (2073 views)
Permalink

Re: Python 2.6.3 [In reply to]

Barry Warsaw wrote:
>
> On Sep 15, 2009, at 9:53 AM, Ronald Oussoren wrote:
>
>> The IDLE issue is IMHO a release blocker, as is issue 6851.
>
> So that leaves 4 release blockers for 2.6.3.
>

What about this bug:
http://bugs.python.org/issue3890
It appears to me that the SSL module is broken in the 2.6.x line on all
platforms in one of its most common uses (non-blocking). It also seems that
the problem and solution are well understood, so the solution would make a
good candidate for 2.6.3?
Tom.

--
View this message in context: http://www.nabble.com/Python-2.6.3-tp25364517p25524412.html
Sent from the Python - python-dev mailing list archive at Nabble.com.

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

janssen at parc

Sep 19, 2009, 1:40 PM

Post #17 of 36 (2084 views)
Permalink

Re: Python 2.6.3 [In reply to]

qwavel <tmm [at] fastmail> wrote:

> What about this bug:
> http://bugs.python.org/issue3890
> It appears to me that the SSL module is broken in the 2.6.x line on all
> platforms in one of its most common uses (non-blocking). It also seems that
> the problem and solution are well understood, so the solution would make a
> good candidate for 2.6.3?
> Tom.

I might quibble about "most common uses", but I agree this would be a good idea.

Bill
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

barry at python

Sep 25, 2009, 1:14 PM

Post #18 of 36 (1951 views)
Permalink

Re: Python 2.6.3 [In reply to]

On Sep 19, 2009, at 2:51 PM, qwavel wrote:

> What about this bug:
> http://bugs.python.org/issue3890
> It appears to me that the SSL module is broken in the 2.6.x line on
> all
> platforms in one of its most common uses (non-blocking). It also
> seems that
> the problem and solution are well understood, so the solution would
> make a
> good candidate for 2.6.3?

I made this a release blocker, but reserve the right to bump it down
again.

-Barry

Attachments:

PGP.sig (0.81 KB)

jnoller at gmail

Sep 25, 2009, 1:18 PM

Post #19 of 36 (1947 views)
Permalink

Re: Python 2.6.3 [In reply to]

On Fri, Sep 25, 2009 at 3:14 PM, Barry Warsaw <barry [at] python> wrote:
> On Sep 19, 2009, at 2:51 PM, qwavel wrote:
>
>> What about this bug:
>> http://bugs.python.org/issue3890
>> It appears to me that the SSL module is broken in the 2.6.x line on all
>> platforms in one of its most common uses (non-blocking). �It also seems
>> that
>> the problem and solution are well understood, so the solution would make a
>> good candidate for 2.6.3?
>
> I made this a release blocker, but reserve the right to bump it down again.
>
> -Barry
>

Barry - this is your call, but I think
http://bugs.python.org/issue6990 should be a rel blocker too.

jesse
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

barry at python

Sep 25, 2009, 1:23 PM

Post #20 of 36 (1932 views)
Permalink

Re: Python 2.6.3 [In reply to]

On Sep 25, 2009, at 4:18 PM, Jesse Noller wrote:

> Barry - this is your call, but I think
> http://bugs.python.org/issue6990 should be a rel blocker too.

Done.
-Barry

Attachments:

PGP.sig (0.81 KB)

nad at acm

Sep 29, 2009, 9:29 PM

Post #21 of 36 (1890 views)
Permalink

Re: Python 2.6.3 [In reply to]

In article <9D506035-7C2D-4929-A134-E88EEB7B7D9E [at] python>,
Barry Warsaw <barry [at] python> wrote:
> On Sep 9, 2009, at 1:29 PM, Ned Deily wrote:
> > The recent release of OS X 10.6 (Snow Leopard) has triggered a fair
> > amount of 2.6 bug tracker activity, since 10.6 now includes 2.6
> > (2.6.1)
> > and a 64-bit version at that. A number of patches have either just
> > been checked-in over the past couple of weeks or are getting some
> > exposure before check-in. Given the timing and the (appropriate)
> > infrequency of 2.6.x releases, I think it would be unfortunate to push
> > 2.6.3 out the door without ensuring that it works well on 10.6.
> > Therefore, I propose that 2.6.3 should have 10.6 compatibility as a
> > "release goal".
> > Without trying to put Ronald on the spot (too much!), it would be a
> > good
> > idea to get his assessment where things stand wrt 2.6 on 10.6 before
> > setting a final release date.
>
> I'm hoping that Python won't have any issues building and running on
> 10.6, but I don't have it yet so I can't personally test it out.
>
> How would you quantify "works well"? Do you have any thoughts on
> tests you'd run other than the standard test suite? If 2.6.3 is shown
> to pass its test suite on 10.5.x, is that good enough? Are the
> specific bug fixes necessary for 10.6?

To follow-up, I've now run the usual "standard" OS X installer builds
and regression tests using 2.6.3rc1 plus a few additional tests (IDLE
and package installation) and have found no regressions from 2.6.2 and
verified that some release-blocker problems have indeed been fixed. In
particular, Issue6957 regarding extensions module building on OS X 10.6
is fixed as discussed in the issue.

The tests involved the target python.org installer configuration:

- deployment target = 10.3, 2-way i386/ppc, Tk 10.4, built on 10.5
-> regrtest on 10.4 ppc, 10.5 ppc, 10.6 i386

plus the following additional configurations:

- deployment target = 10.3, 2-way i386/ppc, Tk 10.4, built on 10.4:
-> regrtest on 10.4 ppc, 10.5 ppc, 10.6 i386

- deployment target = 10.5, 4-way i386/x86_64/ppc/ppc64, Tk 10.4, built
on 10.5:
-> regrtest on 10.5 ppc, 10.6 i386, 10.6 x86_64

plus, a quick check of the currently unsupported configuration, with no
new regressions noted:

- deployment target = 10.6, 2-way i386/x86_64, Tk 10.5, built on 10.6:
-> regrtest on 10.6 x86_64

As noted in various tracker issues, there are still a few unresolved
issues with universal builds built on 10.6 (e.g. 32-bit vs 64-bit
selection, IDLE with Tk 8.5) which is why this last installer build
configuration is currently unsupported.

In my opinion, the standard python.org OS X installer for 2.6.3 now
"works well" on 10.4, 10.5, and 10.6 and is ready for release.

--
Ned Deily,
nad [at] acm

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

barry at python

Sep 30, 2009, 5:34 AM

Post #22 of 36 (1874 views)
Permalink

Re: Python 2.6.3 [In reply to]

On Sep 30, 2009, at 12:29 AM, Ned Deily wrote:

> In my opinion, the standard python.org OS X installer for 2.6.3 now
> "works well" on 10.4, 10.5, and 10.6 and is ready for release.

Fantastic, thanks. Martin's uploaded the Windows binaries so I'll
make the announcement now. No commits to the 2.6 tree are allowed
without checking with me first (via IRC, bug tracker or email). I'll
make an exception for svnmerge bookkeeping.

-Barry

Attachments:

PGP.sig (0.81 KB)

sridharr at activestate

Sep 30, 2009, 12:36 PM

Post #23 of 36 (1868 views)
Permalink

Re: Python 2.6.3 [In reply to]

2.6.3rc1 builds fine on Linux x86/x86_64, MacOSX 10.4 ppc/x86, Windows
32bit/64bit, HP-UX, AIX and Solaris just like 2.6.2 did.

-srid

On Wed, 30 Sep 2009 05:34:02 -0700, Barry Warsaw <barry [at] python> wrote:

> On Sep 30, 2009, at 12:29 AM, Ned Deily wrote:
>
>> In my opinion, the standard python.org OS X installer for 2.6.3 now
>> "works well" on 10.4, 10.5, and 10.6 and is ready for release.
>
> Fantastic, thanks. Martin's uploaded the Windows binaries so I'll
> make the announcement now. No commits to the 2.6 tree are allowed
> without checking with me first (via IRC, bug tracker or email). I'll
> make an exception for svnmerge bookkeeping.
>
> -Barry
>

_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

barry at python

Sep 30, 2009, 12:44 PM

Post #24 of 36 (1858 views)
Permalink

Re: Python 2.6.3 [In reply to]

On Sep 30, 2009, at 3:36 PM, Sridhar Ratnakumar wrote:

> 2.6.3rc1 builds fine on Linux x86/x86_64, MacOSX 10.4 ppc/x86,
> Windows 32bit/64bit, HP-UX, AIX and Solaris just like 2.6.2 did.

Thanks for the feedback! Did you run the test suite on any of these?

-Barry

Attachments:

PGP.sig (0.81 KB)

python at rcn

Sep 30, 2009, 1:03 PM

Post #25 of 36 (1858 views)
Permalink

Re: Python 2.6.3 [In reply to]

[Sridhar Ratnakumar]
> 2.6.3rc1 builds fine on Linux x86/x86_64, MacOSX 10.4 ppc/x86, Windows
> 32bit/64bit, HP-UX, AIX and Solaris just like 2.6.2 did.

Did the test suite pass too?

Raymond
_______________________________________________
Python-Dev mailing list
Python-Dev [at] python
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

1 2

View All

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads