-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A reminder: the second betas of Python 2.6 and 3.0 are schedule for tomorrow. I will try to hang out on #python-dev today and will start looking at the trackers and buildbots. Hopefully, we're on track to get the releases out! If there is anything you need a decision on, please follow up to this thread. I'm inundated with email so I can't watch every thread on the mailing lists. Or ping me on #python-dev. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSHyY5XEjvBPtnXfVAQKvYgP+J4GYVDWOraKhErC4wRl0ylEdHcc9LypB O7yxhBjb+tLu54IImxLkj/Nzff4uUQI6zsA6lg87A4b+sC0/0ltH4+vGkZaq8z7/ xSlP0b0UOaBpOEhTR8ZJK3DJBjSk97IR8Ty3MV1DuM0cczYltorCmQVpodA5ciXj PRy/LAIalJg= =DTQM -----END PGP SIGNATURE-----
On Tue, Jul 15, 2008 at 1:32 PM, Barry Warsaw <barry@python.org> wrote:
If there is anything you need a decision on, please follow up to this thread. I'm inundated with email so I can't watch every thread on the mailing lists. Or ping me on #python-dev.
Can I request permission to check in the patch attached to issue 3008 (float <-> hex) conversion? This is the revised version of the bin/oct/hex for floats patch that Raymond had to withdraw shortly after the first beta. Link to the issue: http://bugs.python.org/issue3008 and the long recent thread on python-dev http://mail.python.org/pipermail/python-dev/2008-June/080558.html Mark
Barry Warsaw wrote:
A reminder: the second betas of Python 2.6 and 3.0 are schedule for tomorrow. I will try to hang out on #python-dev today and will start looking at the trackers and buildbots. Hopefully, we're on track to get the releases out!
If there is anything you need a decision on, please follow up to this thread. I'm inundated with email so I can't watch every thread on the mailing lists. Or ping me on #python-dev.
I'll be checking in the fix for issue 2235 shortly (the problem with __hash__ not being inherited in 2.x). A pre-review from Guido would have been nice (since monkeying with typeobject.c is always a somewhat delicate operation), but it looks like he didn't get a chance to get back to it after Europython. I'm also going to forward port the underlying implementation to Py3k (so that a non-existent hash is indicated by PyObject_HashNotImplemented in tp_hash at the C level as well as by __hash__ = None at the Python level). Cheers, Nick. _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/ncoghlan%40gmail.com -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia --------------------------------------------------------------- http://www.boredomandlaziness.org
Nick Coghlan wrote:
Barry Warsaw wrote:
A reminder: the second betas of Python 2.6 and 3.0 are schedule for tomorrow. I will try to hang out on #python-dev today and will start looking at the trackers and buildbots. Hopefully, we're on track to get the releases out!
If there is anything you need a decision on, please follow up to this thread. I'm inundated with email so I can't watch every thread on the mailing lists. Or ping me on #python-dev.
I'll be checking in the fix for issue 2235 shortly (the problem with __hash__ not being inherited in 2.x). A pre-review from Guido would have been nice (since monkeying with typeobject.c is always a somewhat delicate operation), but it looks like he didn't get a chance to get back to it after Europython.
I'm also going to forward port the underlying implementation to Py3k (so that a non-existent hash is indicated by PyObject_HashNotImplemented in tp_hash at the C level as well as by __hash__ = None at the Python level).
This is now done. There's some documentation updates still to do, as well as adding the Py3k warning back in to the 2.6 version, but I won't have time to do that for this release - I dropped the tracker item down to deferred blocker so it gets back on the list for beta 3. Looking at the buildbots, getting the multiprocessing fixes in looks like it will be a major help in getting more of them to go green, and the import related lib2to3 tests also appear to need some attention. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia --------------------------------------------------------------- http://www.boredomandlaziness.org
On Tue, Jul 15, 2008 at 8:32 AM, Barry Warsaw <barry@python.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
A reminder: the second betas of Python 2.6 and 3.0 are schedule for tomorrow. I will try to hang out on #python-dev today and will start looking at the trackers and buildbots. Hopefully, we're on track to get the releases out!
If there is anything you need a decision on, please follow up to this thread. I'm inundated with email so I can't watch every thread on the mailing lists. Or ping me on #python-dev.
- -Barry
One fix I would like for the upcoming beta is the patch to issue874900 - this seems to have resolved a good chunk of the test_multiprocessing hangs we've been having problems with. I'm in the process of double-checking the latest patch posted by Greg. http://bugs.python.org/issue874900
On Tue, Jul 15, 2008 at 5:32 AM, Barry Warsaw <barry@python.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
A reminder: the second betas of Python 2.6 and 3.0 are schedule for tomorrow. I will try to hang out on #python-dev today and will start looking at the trackers and buildbots. Hopefully, we're on track to get the releases out!
If there is anything you need a decision on, please follow up to this thread. I'm inundated with email so I can't watch every thread on the mailing lists. Or ping me on #python-dev.
The new urllib package landed between the last beta and now, but without fixers. Issue3316 has potential ones, but they have some tweaks that need to be made before they are release quality. If the beta goes out 2to3 will not be able to fix imports for urllib and urllib2. Don't know if that is enough to hold up the release or just something to put in the release notes that this will be resolved by the next beta; made it a release blocker to catch your eye, Barry. =) Oh, and fixers for test.test_support to test.support is not in either, but this is probably such a small use case outside the core that I am not sweating bullets for writing a new fixer just for this one case. -Brett
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I realized that the previous schedule really called for a release today 7/15 because I'm a bit busy tomorrow night. In any event, let's try to stick to doing it on 7/16. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSH012XEjvBPtnXfVAQLJiQQAiP+/S1KVuv9ZgzyS7XdQNW2USTcBGkCh LIQs3Z+ueuZ9MORdwuDnuZmJWpxataYe26UiPKxt8BFJO81x1i7hy4/uvrO4aE+z doksz9eJtclNWQNAcvgRX2bKM0OBO57egJrqxYFUgqlziELxOT/U2//josdl3jR1 ovOb/C0nWVU= =LBea -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jul 15, 2008, at 2:38 PM, Brett Cannon wrote:
On Tue, Jul 15, 2008 at 5:32 AM, Barry Warsaw <barry@python.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
A reminder: the second betas of Python 2.6 and 3.0 are schedule for tomorrow. I will try to hang out on #python-dev today and will start looking at the trackers and buildbots. Hopefully, we're on track to get the releases out!
If there is anything you need a decision on, please follow up to this thread. I'm inundated with email so I can't watch every thread on the mailing lists. Or ping me on #python-dev.
The new urllib package landed between the last beta and now, but without fixers. Issue3316 has potential ones, but they have some tweaks that need to be made before they are release quality. If the beta goes out 2to3 will not be able to fix imports for urllib and urllib2. Don't know if that is enough to hold up the release or just something to put in the release notes that this will be resolved by the next beta; made it a release blocker to catch your eye, Barry. =)
I knocked this down to a deferred blocker, so I won't let it hold up beta2, though I'd /really/ like to get this cleaned up and committed in time. If I get enough deferred blockers though, I might hold things up after all.
Oh, and fixers for test.test_support to test.support is not in either, but this is probably such a small use case outside the core that I am not sweating bullets for writing a new fixer just for this one case.
Ok. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSH02pnEjvBPtnXfVAQL1qgP/a2yf6fagOS7Hvbwd08ZhYkaB+GDTcFMy mo/bJtvrdCRwPm+60q5mZYuMBIz/I7IBSQmSI09IOdEi0RPoXH6Los3LMrt+Aa6v XgPu7nYcO1vNa/b+6vNvsBAEPfEuaMJsSRpHNJfAWsjF82BsiNEpJ0D5906CAhyW MrjaPUb47bs= =/qoQ -----END PGP SIGNATURE-----
On Tue, Jul 15, 2008 at 4:45 PM, Barry Warsaw <barry@python.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jul 15, 2008, at 2:38 PM, Brett Cannon wrote:
On Tue, Jul 15, 2008 at 5:32 AM, Barry Warsaw <barry@python.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
A reminder: the second betas of Python 2.6 and 3.0 are schedule for tomorrow. I will try to hang out on #python-dev today and will start looking at the trackers and buildbots. Hopefully, we're on track to get the releases out!
If there is anything you need a decision on, please follow up to this thread. I'm inundated with email so I can't watch every thread on the mailing lists. Or ping me on #python-dev.
The new urllib package landed between the last beta and now, but without fixers. Issue3316 has potential ones, but they have some tweaks that need to be made before they are release quality. If the beta goes out 2to3 will not be able to fix imports for urllib and urllib2. Don't know if that is enough to hold up the release or just something to put in the release notes that this will be resolved by the next beta; made it a release blocker to catch your eye, Barry. =)
I knocked this down to a deferred blocker, so I won't let it hold up beta2, though I'd /really/ like to get this cleaned up and committed in time. If I get enough deferred blockers though, I might hold things up after all.
Nick is actively working on it, so it might make it in b2. -Brett
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jul 15, 2008, at 8:32 AM, Barry Warsaw wrote:
If there is anything you need a decision on, please follow up to this thread. I'm inundated with email so I can't watch every thread on the mailing lists. Or ping me on #python-dev.
I'm not currently optimistic that we can release today. As I see it we have several problems serious enough to delay a release. First, we have no green 2.6 or 3.0 buildbots http://www.python.org/dev/buildbot/stable/ It looks like few of the buildbots for 2.6 are actually online, but still, the 3.0 buildbots are all failing. We still have, and have had for a long time now, serious problems with the multiprocessing module: http://bugs.python.org/issue?@columns=title,id,activity,versions,status&@sort=activity&@filter=priority,status&@pagesize=50&@startwith=0&priority=1&status=1&@dispname=Showstoppers I noticed today that _multiprocessing.so has build problems on OS X 10.5 and Ubuntu 8.04. I opened a separate issue about that so as not to get lost in the other bug about test_multiprocessing hanging. As evidenced by the thread for issue 3088, lots of people have put a lot of work into this module, but unfortunately we're still not there. These seem serious enough to me to hold up the release, especially since we have only one more beta left. Speaking of which, we have a number of deferred blockers: http://bugs.python.org/issue?@columns=title,id,activity,status&@sort=activity&@group=priority&@filter=priority,status&@pagesize=50&@startwith=0&priority=6&status=1&@dispname=Deferred%20Blockers These will not block beta 2, but they /will/ block beta 3, so they really need some attention. Please everyone, if you have only a little bit of time to work on Python, I hope you will attack the release critical and deferred blocker issues, and work on turning the buildbots green. These are the top priorities in order to get 2.6 and 3.0 out on time. And just as added incentive, our October 1st goal is being noted by downstream vendors. I've been told that "Apple is willing to take the new Python if it is GM on schedule by Oct 1st, but may not if it is delayed" though you should not infer anything about Apple's schedule from this. Still, we won't sacrifice quality in order to hit the October 1st goal. After beta 2, I start getting mean. :) - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSH31HHEjvBPtnXfVAQIH+AQAtkRJo0uhvZ300jq0YSR6ezUU0tMHJwmd pwLWwZWDqPyh3/ohKwrajdGm5hYS8gOnTo+k2XEEJjQJdLMTblzZ3ArsGfhXHqbV GPeKK/6BYT6SOD75ubINq+jSsu6Pvjsadbk/cp/x53WwHL8kX40D0YQBhp3KQRrz zgFmfVFPcys= =3SDN -----END PGP SIGNATURE-----
participants (5)
-
Barry Warsaw -
Brett Cannon -
Jesse Noller -
Mark Dickinson -
Nick Coghlan