Re: [Python-Dev] please take a look at buildbot result [was: Broken link to download (Mac OS X)]
On 29 Apr, 2010, at 20:28, Bill Janssen wrote: > Michael Foord wrote: > >> Well - I have nine failing tests on trunk for Mac OS X with Snow Leopard. >> >> 9 tests failed: >>test_cmd_line test_imp test_import test_posix test_pydoc >>test_runpy test_urllib2 test_urllib2_localnet test_warnings >> >> I believe that Victor has ensured that the buildbot failures have open >> issues against, I'm just going to check that the failures I see are >> the same. > > Just built on Intel/Leopard with the trunk (almost vanilla, except for > _ssl.c) and tested. Here's what I configured: > > ./configure --prefix=/local/python/trunk --disable-universalsdk > --disable-framework --disable-toolbox-glue --with-pydebug > > ... > 8 skips unexpected on darwin: >test_aepack test_applesingle test_gdb test_macos test_macostools >test_readline test_scriptpackages test_ttk_guionly > > Why is the skip of "test_readline" unexpected on darwin? The readline > on Darwin isn't what Python wants. The skip of test_readline is unexpected because readline should have been build with the options above and tests should have worked. Ronald smime.p7s Description: S/MIME cryptographic signature ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Summary of Python tracker Issues
ACTIVITY SUMMARY (2010-04-23 - 2010-04-30) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. 2638 open (+41) / 17759 closed (+27) / 20397 total (+68) Open issues with patches: 1081 Average duration of open issues: 724 days. Median duration of open issues: 494 days. Open Issues Breakdown open 2620 (+41) languishing10 ( +0) pending 7 ( +0) Issues Created Or Reopened (71) ___ "Report bug" links 2010-04-24 CLOSED http://bugs.python.org/issue2823reopened techtonik Silence DeprecationWarning by default 2010-04-25 http://bugs.python.org/issue7319reopened benjamin.peterson patch Small mistake in tutorial web page 2010-04-23 CLOSED http://bugs.python.org/issue8511created mdcowles os.execv*e(): fix formatting of the environment variables (Pyt 2010-04-23 CLOSED http://bugs.python.org/issue8512created haypo patch subprocess: support bytes program name 2010-04-23 http://bugs.python.org/issue8513created haypo patch Create fsencode() and fsdecode() functions in os.path 2010-04-23 http://bugs.python.org/issue8514created haypo patch idle "Run Module" (F5) does not set __file__ variable 2010-04-24 http://bugs.python.org/issue8515created dangyogi patch Speed difference between Python 2.5 and 2.6 during filling bsd 2010-04-24 http://bugs.python.org/issue8516created PeterL Apple Style Guide link is broken in the "Documenting Python" c 2010-04-24 CLOSED http://bugs.python.org/issue8517created brandon-rhodes small typo in http://docs.python.org/howto/doanddont.html 2010-04-24 CLOSED http://bugs.python.org/issue8518created Adrián.Deccico [patch] doc: termios and ioctl reference links 2010-04-24 http://bugs.python.org/issue8519created techtonik patch test doc issue 2010-04-24 CLOSED http://bugs.python.org/issue8520created georg.brandl Allow some winreg functions to accept keyword arguments2010-04-24 http://bugs.python.org/issue8521created brian.curtin patch enhacement proposal in howto/doanddont 2010-04-24 CLOSED http://bugs.python.org/issue8522created Adrián.Deccico patch shutil.rmtree and os.listdir cannot recover on error condition 2010-04-24 http://bugs.python.org/issue8523created rubenlm easy SSL sockets do not retain the parent socket's attributes 2010-04-24 http://bugs.python.org/issue8524created pitrou Small enhancement to help()2010-04-24 http://bugs.python.org/issue8525created robcliffe msilib doesn't support multiple CAB instances in same installe 2010-04-25 http://bugs.python.org/issue8526created janssen easy [PEP 3147] compileall.compile
Re: [Python-Dev] Two small PEP ideas
On Apr 28, 2010, at 09:22 AM, Dirkjan Ochtman wrote: >On Tue, Apr 27, 2010 at 23:55, Nick Coghlan wrote: >> I believe the more important part of Barry's suggested change here is >> requiring a link to the archived message (usually from python-dev) where >> the PEP was accepted (be it directly by you as BDFL, or by consensus >> from a "sufficient" number of core developers). This will likely also >> help with reminding people to announce on python-dev when PEPs are >> accepted by consensus (or by you) somewhere like PyCon or a sprint. > >Though maybe it should be called Conclusion instead of Accepted and >used for Rejected PEPs, as well? Good point. What do you think about 'Resolution'? As to Guido's point about the decision making process, Nick's right. I just want to make sure we can capture the resolution in the PEP, be it by BDFL pronouncement or "hey, silence is acceptance" email. Cheers, -Barry signature.asc Description: PGP signature ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
> As to Guido's point about the decision making process, Nick's right. I just > want to make sure we can capture the resolution in the PEP, be it by BDFL > pronouncement or "hey, silence is acceptance" email. I don't think "silence is acceptance" will work out in practice. For issues where a PEP was written in the first place, somebody will *always* object, and forever so, hoping that what he considers a mistake will not be done. The advantage of Guido acting as BDFL was that somebody would make an decision ultimately, one which both proponents and opponents of the PEP would accept. Without a BDFL, I think we need a committee to make decisions, e.g. by majority vote amongst committers. Regards, Martin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
Martin v. Löwis wrote: >> As to Guido's point about the decision making process, Nick's right. I just >> want to make sure we can capture the resolution in the PEP, be it by BDFL >> pronouncement or "hey, silence is acceptance" email. > > I don't think "silence is acceptance" will work out in practice. For > issues where a PEP was written in the first place, somebody will > *always* object, and forever so, hoping that what he considers a mistake > will not be done. The advantage of Guido acting as BDFL was that > somebody would make an decision ultimately, one which both proponents > and opponents of the PEP would accept. > > Without a BDFL, I think we need a committee to make decisions, e.g. by > majority vote amongst committers. Couldn't we just go with the FLUFL? regards Steve -- Steve Holden +1 571 484 6266 +1 800 494 3119 See PyCon Talks from Atlanta 2010 http://pycon.blip.tv/ Holden Web LLC http://www.holdenweb.com/ UPCOMING EVENTS:http://holdenweb.eventbrite.com/ ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
On Fri, Apr 30, 2010 at 1:28 PM, Steve Holden wrote: > Martin v. Löwis wrote: >>> As to Guido's point about the decision making process, Nick's right. I just >>> want to make sure we can capture the resolution in the PEP, be it by BDFL >>> pronouncement or "hey, silence is acceptance" email. >> >> I don't think "silence is acceptance" will work out in practice. For >> issues where a PEP was written in the first place, somebody will >> *always* object, and forever so, hoping that what he considers a mistake >> will not be done. The advantage of Guido acting as BDFL was that >> somebody would make an decision ultimately, one which both proponents >> and opponents of the PEP would accept. >> >> Without a BDFL, I think we need a committee to make decisions, e.g. by >> majority vote amongst committers. > > Couldn't we just go with the FLUFL? IIRC in the IETF this is done by the committee chair. I think it's a good idea to have this be a single person to avoid endless indecision. > regards > Steve > -- > Steve Holden +1 571 484 6266 +1 800 494 3119 > See PyCon Talks from Atlanta 2010 http://pycon.blip.tv/ > Holden Web LLC http://www.holdenweb.com/ > UPCOMING EVENTS: http://holdenweb.eventbrite.com/ > > ___ > Python-Dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (python.org/~guido) ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
>> Without a BDFL, I think we need a committee to make decisions, e.g. by >> majority vote amongst committers. > > Couldn't we just go with the FLUFL? Not sure whether that's a serious proposal (April 1 is already some days back now). As a starting point, Barry would have to indicate whether he is interested in that role. Regards, Martin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
Martin v. Löwis wrote: >>> Without a BDFL, I think we need a committee to make decisions, e.g. by >>> majority vote amongst committers. >> Couldn't we just go with the FLUFL? > > Not sure whether that's a serious proposal (April 1 is already some days > back now). As a starting point, Barry would have to indicate whether he > is interested in that role. > If he isn't then we can depose him and replace him with a puppet. regards Steve PS: Barry: sorry I can't make the gig tonight. Hope it went well ... -- Steve Holden +1 571 484 6266 +1 800 494 3119 See PyCon Talks from Atlanta 2010 http://pycon.blip.tv/ Holden Web LLC http://www.holdenweb.com/ UPCOMING EVENTS:http://holdenweb.eventbrite.com/ ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
Steve Holden wrote: > Martin v. Löwis wrote: Without a BDFL, I think we need a committee to make decisions, e.g. by majority vote amongst committers. >>> Couldn't we just go with the FLUFL? >> Not sure whether that's a serious proposal (April 1 is already some days >> back now). As a starting point, Barry would have to indicate whether he >> is interested in that role. >> > If he isn't then we can depose him and replace him with a puppet. Ah, ok. So you didn't mean that seriously; a smiley would have helped. Regards, Martin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] patch for review: __import__ documentation
> I see the confusion. I think Martin meant more about open issues that > required discussion, not simply issues that had a patch ready to go. I actually think it is perfectly fine to point out that specific issues are need committer action on this list. This is what the list is there for. Waiting some time to see whether some developer reacts is certainly a good idea: notice, however, that Chris had already waited a few days. Regards, Martin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
On Apr 30, 2010, at 3:51 PM, "Martin v. Löwis" wrote: As to Guido's point about the decision making process, Nick's right. I just want to make sure we can capture the resolution in the PEP, be it by BDFL pronouncement or "hey, silence is acceptance" email. I don't think "silence is acceptance" will work out in practice. For issues where a PEP was written in the first place, somebody will *always* object, and forever so, hoping that what he considers a mistake will not be done. The advantage of Guido acting as BDFL was that somebody would make an decision ultimately, one which both proponents and opponents of the PEP would accept. Without a BDFL, I think we need a committee to make decisions, e.g. by majority vote amongst committers. Regards, Martin Consider this a plaintitive -1 to any sort of rule-or-decision based on committee. I'd much rather a 2x4 to the forehead. jesse ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
Jesse Noller gmail.com> writes: > > Consider this a plaintitive -1 to any sort of rule-or-decision based > on committee. > > I'd much rather a 2x4 to the forehead. Oops, sorry but what does "a 2x4 to the forehead" mean? (and "plaintitive" by the way?) Regards Antoine. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
2010/4/30 Antoine Pitrou : > Jesse Noller gmail.com> writes: >> >> Consider this a plaintitive -1 to any sort of rule-or-decision based >> on committee. >> >> I'd much rather a 2x4 to the forehead. > > Oops, sorry but what does "a 2x4 to the forehead" mean? > (and "plaintitive" by the way?) The former means being hit by a board and by the latter, he probably means "plaintive" meaning melancholy. -- Regards, Benjamin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
On Fri, Apr 30, 2010 at 5:08 PM, Benjamin Peterson wrote: > 2010/4/30 Antoine Pitrou : >> Jesse Noller gmail.com> writes: >>> >>> Consider this a plaintitive -1 to any sort of rule-or-decision based >>> on committee. >>> >>> I'd much rather a 2x4 to the forehead. >> >> Oops, sorry but what does "a 2x4 to the forehead" mean? >> (and "plaintitive" by the way?) > > The former means being hit by a board and by the latter, he probably > means "plaintive" meaning melancholy. > Does it only work for english speaking non-metric system users? (2x4 is probably something imperial) ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
On 01/05/2010 00:08, Benjamin Peterson wrote: 2010/4/30 Antoine Pitrou: Jesse Noller gmail.com> writes: Consider this a plaintitive -1 to any sort of rule-or-decision based on committee. I'd much rather a 2x4 to the forehead. Oops, sorry but what does "a 2x4 to the forehead" mean? (and "plaintitive" by the way?) The former means being hit by a board and by the latter, he probably means "plaintive" meaning melancholy. And 2x4 refers to a board with cross-section of 4 inches x 2 inches; the inch being an obsolete unit of measure from the old British imperial system now defunct throughout the civilized world. Michael -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
On 01/05/2010 00:10, Maciej Fijalkowski wrote: On Fri, Apr 30, 2010 at 5:08 PM, Benjamin Peterson wrote: 2010/4/30 Antoine Pitrou: Jesse Noller gmail.com> writes: Consider this a plaintitive -1 to any sort of rule-or-decision based on committee. I'd much rather a 2x4 to the forehead. Oops, sorry but what does "a 2x4 to the forehead" mean? (and "plaintitive" by the way?) The former means being hit by a board and by the latter, he probably means "plaintive" meaning melancholy. Does it only work for english speaking non-metric system users? (2x4 is probably something imperial) You we would probably strike with 100x50mm boards instead. Michael ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
2010/4/30 Maciej Fijalkowski : > On Fri, Apr 30, 2010 at 5:08 PM, Benjamin Peterson > wrote: >> 2010/4/30 Antoine Pitrou : >>> Jesse Noller gmail.com> writes: Consider this a plaintitive -1 to any sort of rule-or-decision based on committee. I'd much rather a 2x4 to the forehead. >>> >>> Oops, sorry but what does "a 2x4 to the forehead" mean? >>> (and "plaintitive" by the way?) >> >> The former means being hit by a board and by the latter, he probably >> means "plaintive" meaning melancholy. >> > > Does it only work for english speaking non-metric system users? (2x4 > is probably something imperial) Yes, that's a 5,04 by 10,08 for you. :) -- Regards, Benjamin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
On Fri, Apr 30, 2010 at 4:14 PM, Benjamin Peterson wrote: > 2010/4/30 Maciej Fijalkowski : >> On Fri, Apr 30, 2010 at 5:08 PM, Benjamin Peterson >> wrote: >>> 2010/4/30 Antoine Pitrou : Jesse Noller gmail.com> writes: > > Consider this a plaintitive -1 to any sort of rule-or-decision based > on committee. > > I'd much rather a 2x4 to the forehead. Oops, sorry but what does "a 2x4 to the forehead" mean? (and "plaintitive" by the way?) >>> >>> The former means being hit by a board and by the latter, he probably >>> means "plaintive" meaning melancholy. >>> >> >> Does it only work for english speaking non-metric system users? (2x4 >> is probably something imperial) > > Yes, that's a 5,04 by 10,08 for you. :) Of course "2 by 4" is just the name. The actual measurements of such a piece of lumber in the store are about 1.75 by 3.75 inch. :-) -- --Guido van Rossum (python.org/~guido) ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
Michael Foord wrote: > On 01/05/2010 00:08, Benjamin Peterson wrote: >> 2010/4/30 Antoine Pitrou: >> >>> Jesse Noller gmail.com> writes: >>> Consider this a plaintitive -1 to any sort of rule-or-decision based on committee. I'd much rather a 2x4 to the forehead. >>> Oops, sorry but what does "a 2x4 to the forehead" mean? >>> (and "plaintitive" by the way?) >>> >> The former means being hit by a board and by the latter, he probably >> means "plaintive" meaning melancholy. >> >> > And 2x4 refers to a board with cross-section of 4 inches x 2 inches; the > inch being an obsolete unit of measure from the old British imperial > system now defunct throughout the civilized world. > The last time I was in a UK builders' yard I hear someone asking for "two meter pieces of two by four". At the time the UK was notionally metric (and the timber was planed to the nearest metric size) but the old names still survived. regards Steve -- Steve Holden +1 571 484 6266 +1 800 494 3119 See PyCon Talks from Atlanta 2010 http://pycon.blip.tv/ Holden Web LLC http://www.holdenweb.com/ UPCOMING EVENTS:http://holdenweb.eventbrite.com/ ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
On Fri, Apr 30, 2010 at 9:11 PM, Guido van Rossum wrote: > On Fri, Apr 30, 2010 at 4:14 PM, Benjamin Peterson > wrote: >> 2010/4/30 Maciej Fijalkowski : >>> On Fri, Apr 30, 2010 at 5:08 PM, Benjamin Peterson >>> wrote: 2010/4/30 Antoine Pitrou : > Jesse Noller gmail.com> writes: >> >> Consider this a plaintitive -1 to any sort of rule-or-decision based >> on committee. >> >> I'd much rather a 2x4 to the forehead. > > Oops, sorry but what does "a 2x4 to the forehead" mean? > (and "plaintitive" by the way?) The former means being hit by a board and by the latter, he probably means "plaintive" meaning melancholy. >>> >>> Does it only work for english speaking non-metric system users? (2x4 >>> is probably something imperial) >> >> Yes, that's a 5,04 by 10,08 for you. :) > > Of course "2 by 4" is just the name. The actual measurements of such a > piece of lumber in the store are about 1.75 by 3.75 inch. :-) > We americans round up! (all the time) ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
On Fri, Apr 30, 2010 at 7:08 PM, Benjamin Peterson wrote: > 2010/4/30 Antoine Pitrou : >> Jesse Noller gmail.com> writes: >>> >>> Consider this a plaintitive -1 to any sort of rule-or-decision based >>> on committee. >>> >>> I'd much rather a 2x4 to the forehead. >> >> Oops, sorry but what does "a 2x4 to the forehead" mean? >> (and "plaintitive" by the way?) > > The former means being hit by a board and by the latter, he probably > means "plaintive" meaning melancholy. Yes, well, what Benjamin said. jesse ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
Steve Holden wrote: > The last time I was in a UK builders' yard I hear someone asking for > "two meter pieces of two by four". At the time the UK was notionally > metric (and the timber was planed to the nearest metric size) but the > old names still survived. Yeah, a 2x4 is still a 2x4 here as well. It's English, even the native speakers don't really expect it to make sense all the time ;) Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia --- ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Two small PEP ideas
> IIRC in the IETF this is done by the committee chair. I think it's a > good idea to have this be a single person to avoid endless indecision. It then seems that this role should go to the release manager of the upcoming feature release. Assuming Georg can accept this additional responsibility. Regards, Martin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
