-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'd like to get Python 3.0.1 out before the end of the year. There are no showstoppers, but I haven't yet looked at the deferred blockers or the buildbots. Do you think we can get 3.0.1 out on December 24th? Or should we wait until after Christmas and get it out, say on the 29th? Do we need an rc? This question goes mostly to Martin and Georg. What would work for you guys? - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSUwgEXEjvBPtnXfVAQIthgP7BDS6xfBHhADKc50ANvZ5aAfWhGSU9GH/ DR+IRduVmvosu9gm92hupCOaLCN4IbtyFx27A8LQuPNVc4BVrhWfDKDSzpxO2MJu xLJntkF2BRWODSbdrLGdZ6H6WDT0ZAhn6ZjlWXwxhGxQ5FwEJb7moMuY7jAIEeor 5n6Ag5zT+e8= =oU/g -----END PGP SIGNATURE-----
Barry Warsaw wrote:
I'd like to get Python 3.0.1 out before the end of the year. There are no showstoppers, but I haven't yet looked at the deferred blockers or the buildbots.
Do you think we can get 3.0.1 out on December 24th? Or should we wait until after Christmas and get it out, say on the 29th? Do we need an rc?
There are some memoryview issues [1] I'd like to have fixed for 3.0.1 - the 29th would be a much easier date to hit. A quick review pass through the other 3.0 highs and criticals might also be worthwhile. Cheers, Nick. http://bugs.python.org/issue4580 -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia ---------------------------------------------------------------
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Dec 19, 2008, at 5:42 PM, Nick Coghlan wrote:
Barry Warsaw wrote:
I'd like to get Python 3.0.1 out before the end of the year. There are no showstoppers, but I haven't yet looked at the deferred blockers or the buildbots.
Do you think we can get 3.0.1 out on December 24th? Or should we wait until after Christmas and get it out, say on the 29th? Do we need an rc?
There are some memoryview issues [1] I'd like to have fixed for 3.0.1 - the 29th would be a much easier date to hit. A quick review pass through the other 3.0 highs and criticals might also be worthwhile.
Thanks. I've bumped that to release blocker for now. If there are any other 'high' bugs that you want considered for 3.0.1, please make the release blockers too, for now. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSUwkRnEjvBPtnXfVAQKQ4QP/eRmWBgyuijbe9vnXkRkTkAmd4qyrAD2s Forp4hKGvoc4A03Q4x2uVweI4oSdFrKIN2NlcM3JVlSrsU07DTElFoCEA/A8DB3N +6Sp9bC98iVqGUmle54rFIm0F/iCoFQ59mp9jNGeiKVwjojUDkbJNXulHuYIb1co RuICfsatRc0= =zjQz -----END PGP SIGNATURE-----
Barry Warsaw wrote:
Thanks. I've bumped that to release blocker for now. If there are any other 'high' bugs that you want considered for 3.0.1, please make the release blockers too, for now.
I think wsgiref package needs to be fixed. For now it's totally broken. I've already found 4 issues about that: http://bugs.python.org/issue3348 http://bugs.python.org/issue3401 http://bugs.python.org/issue3795 http://bugs.python.org/issue4522 What needs to be fixed: 1. Headers handling in wsgiref.simple_server. Not so hard actually - in a few places headers expected as a list object instead of a dict. 2. wsgiref.handlers should support bytes instead of str. I think WSGI applications must return bytes as a result but we can allow Unicode strings in start_response() because the resulting encoding for headers is known and strings can be safely encoded. So the fix won't be so hard too - few asserts needs to be fixed and headers output needs to be directed through auxiliary encoding method. 3. Tests 4. Documentation examples. I can create the patch before December 24th if needed. -- Dmitry Vasiliev <dima at hlabs.spb.ru> http://hlabs.spb.ru
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Dec 21, 2008, at 6:56 AM, Dmitry Vasiliev wrote:
Barry Warsaw wrote:
Thanks. I've bumped that to release blocker for now. If there are any other 'high' bugs that you want considered for 3.0.1, please make the release blockers too, for now.
I think wsgiref package needs to be fixed. For now it's totally broken. I've already found 4 issues about that:
http://bugs.python.org/issue3348 http://bugs.python.org/issue3401 http://bugs.python.org/issue3795 http://bugs.python.org/issue4522
Please make sure these issues are release blockers. Fixes before January 5th would be able to make it into 3.0.1. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSU+9U3EjvBPtnXfVAQII5wP+M9tyL169XMIwoibqupyPErAjHNL+zWD1 wydak1MKc/gF6KvSFfs9t6uuI3p8GI42dNxeHXIXsCb1he16YfUgu7xG210ZJ9C3 YkDcr6vDDMYUvMI8XdVJGh9ASnQhrQRiyMI/TtiJTh16t3wnn78EH2F2IyrYcDrD 0xaKQjaK1+k= =t6EL -----END PGP SIGNATURE-----
Barry Warsaw <barry <at> python.org> writes:
Please make sure these issues are release blockers. Fixes before January 5th would be able to make it into 3.0.1.
Should http://bugs.python.org/issue4486 be a release blocker as well? (I don't think so, but...)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Dec 22, 2008, at 11:38 AM, Antoine Pitrou wrote:
Barry Warsaw <barry <at> python.org> writes:
Please make sure these issues are release blockers. Fixes before January 5th would be able to make it into 3.0.1.
Should http://bugs.python.org/issue4486 be a release blocker as well? (I don't think so, but...)
I don't think so either. It would be nice to have, but it needn't hold up the release. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSU/HgnEjvBPtnXfVAQKzcAP+NThqngryODxF/bKpeMs/EhpjfI9HV4eC Lul5LMocaxEe91ontMjhfnZQo6Tx/jJCGECzVLCLXVmrjKg7/d6/9TFEByc9OWFm zODpRvQ+4u+jd8c8DcBQmEwuFJF4MQZ5x6SUP8HxRTLmWq1KMcGM5WTNHCxMoOVw Gkg8JmknqjM= =6teE -----END PGP SIGNATURE-----
Nick Coghlan <ncoghlan <at> gmail.com> writes:
There are some memoryview issues [1] I'd like to have fixed for 3.0.1 - the 29th would be a much easier date to hit. A quick review pass through the other 3.0 highs and criticals might also be worthwhile.
What about #1717 "Get rid of more refercenes to __cmp__"? (although I like the typo a lot)
Do you think we can get 3.0.1 out on December 24th?
I won't have physical access to my build machine from December 24th to January 3rd.
Or should we wait until after Christmas and get it out, say on the 29th? Do we need an rc?
If you want to get it quickly, it should happen on December 23rd (my time, meaning that the tag should be created on December 22nd). December 29th might work as well; I'd create the binaries remotely (in this case, the tag would need to be created on December 28th). Overall, I think a week more or less doesn't really matter, and would prefer to see the release created in January. There are 13 release blockers, and I'm skeptical that they can all get resolved within the next few days. Regards, Martin
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Dec 19, 2008, at 9:44 PM, Martin v. Löwis wrote:
Do you think we can get 3.0.1 out on December 24th?
I won't have physical access to my build machine from December 24th to January 3rd.
Okay. Let's just push it until after the new year then. In the mean time, please continue to work on fixes for 3.0.1. I'm thinking tentatively to do a release the week of January 5th. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSU+9IHEjvBPtnXfVAQL0vQQAmxcMDP1GUuhCOxCVHqnSGaywdG1mz3f0 iNCNs4lVsRLYV/AVdf/tbpWyLbcUvFL0hUyLDp8PCScOjZReKwe6VpnujL/BwU5E 4P7RtUn493QGqkFJDjHNJ2SIcxOfzk9Y7E3qyS0QHPmsqmNpSD6ZQQd0PkdCoqQo f08Z9HrKZZw= =ujaK -----END PGP SIGNATURE-----
Barry Warsaw schrieb:
I'd like to get Python 3.0.1 out before the end of the year. There are no showstoppers, but I haven't yet looked at the deferred blockers or the buildbots.
Do you think we can get 3.0.1 out on December 24th? Or should we wait until after Christmas and get it out, say on the 29th? Do we need an rc?
This question goes mostly to Martin and Georg. What would work for you guys?
Since the 24th is the most important Christmas day around here, I'll not be available then :) Either 23rd or 29th is fine with me. Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out.
4631 should be a release blocker. I'll have a bit of time on Monday and Tuesday to wrap it up. Jeremy On Fri, Dec 19, 2008 at 5:28 PM, Barry Warsaw <barry@python.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I'd like to get Python 3.0.1 out before the end of the year. There are no showstoppers, but I haven't yet looked at the deferred blockers or the buildbots.
Do you think we can get 3.0.1 out on December 24th? Or should we wait until after Christmas and get it out, say on the 29th? Do we need an rc?
This question goes mostly to Martin and Georg. What would work for you guys?
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSUwgEXEjvBPtnXfVAQIthgP7BDS6xfBHhADKc50ANvZ5aAfWhGSU9GH/ DR+IRduVmvosu9gm92hupCOaLCN4IbtyFx27A8LQuPNVc4BVrhWfDKDSzpxO2MJu xLJntkF2BRWODSbdrLGdZ6H6WDT0ZAhn6ZjlWXwxhGxQ5FwEJb7moMuY7jAIEeor 5n6Ag5zT+e8= =oU/g -----END PGP SIGNATURE----- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/jeremy%40alum.mit.edu
participants (7)
-
"Martin v. Löwis" -
Antoine Pitrou -
Barry Warsaw -
Dmitry Vasiliev -
Georg Brandl -
Jeremy Hylton -
Nick Coghlan