[Python-Dev] Frequency of the dev docs autobuild
Does the online dev version of the docs build in response to docs checkins, or just once a day? (And is that written down somewhere and I've just forgotten where to look...) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia --- ___ 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/archive%40mail-archive.com
Re: [Python-Dev] Frequency of the dev docs autobuild
On Thu, 29 Apr 2010 20:16:14 +1000, Nick Coghlan wrote: > Does the online dev version of the docs build in response to docs > checkins, or just once a day? I believe it does it once a day. Georg recently changed how this is done, so we should get official word from him. > (And is that written down somewhere and I've just forgotten where to > look...) I don't think so, but it should be. -- R. David Murray www.bitdance.com ___ 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/archive%40mail-archive.com
[Python-Dev] please take a look at buildbot result [was: Broken link to download (Mac OS X)]
Ned Deily wrote: > In article <19399.11323.946604.992...@montanaro.dyndns.org>, > s...@pobox.com wrote: > > > Ned> Any idea what type of machine it is and where it is currently > > Ned> located? > > > > I seem to recall it is/was a G4 XServe. My guess as to location would be at > > xs4all.nl. > > If it were working that could be of use. It would not be able to run OS > X 10.6 but having a 10.5 system PPC system as a buildbot would certainly > be useful; it should be fine for the default installer configuration > builds. (Alas, I don't expect to be anywhere in the vicinity in the > foreseeable future.) I've identified 4 G4/G5 machines at PARC I can set up as build slaves on either Tiger or Leopard, and the first one of those is up (G4/Tiger) and running. Can someone (Ned?) take a look at the output and see if the errors are currently expected, or if I need to do more config/install work? I'm using Xcode 2.5. If it's good, I'll go to work on more. The build slave name is "parc-tiger-1". Thanks! Bill ___ 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/archive%40mail-archive.com
[Python-Dev] Tiger buildbots
Le Thu, 29 Apr 2010 07:39:22 -0700, Bill Janssen a écrit : > > I've identified 4 G4/G5 machines at PARC I can set up as build slaves on > either Tiger or Leopard, and the first one of those is up (G4/Tiger) and > running. Can someone (Ned?) take a look at the output and see if the > errors are currently expected, or if I need to do more config/install > work? I'm using Xcode 2.5. If it's good, I'll go to work on more. No failures are currently expected, but the other Tiger buildbot is seeing the same ones as yours. In any case, somebody needs to investigate why these tests fail under Tiger, and I suppose the buildbot owners are in the best position to do so. Regards Antoine. ___ 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/archive%40mail-archive.com
Re: [Python-Dev] please take a look at buildbot result [was: Broken link to download (Mac OS X)]
On 29 Apr, 2010, at 16:39, Bill Janssen wrote: > Ned Deily wrote: > >> In article <19399.11323.946604.992...@montanaro.dyndns.org>, >> s...@pobox.com wrote: >> >>>Ned> Any idea what type of machine it is and where it is currently >>>Ned> located? >>> >>> I seem to recall it is/was a G4 XServe. My guess as to location would be at >>> xs4all.nl. >> >> If it were working that could be of use. It would not be able to run OS >> X 10.6 but having a 10.5 system PPC system as a buildbot would certainly >> be useful; it should be fine for the default installer configuration >> builds. (Alas, I don't expect to be anywhere in the vicinity in the >> foreseeable future.) > > I've identified 4 G4/G5 machines at PARC I can set up as build slaves > on either Tiger or Leopard, and the first one of those is up (G4/Tiger) > and running. Can someone (Ned?) take a look at the output and see if > the errors are currently expected, or if I need to do more > config/install work? I'm using Xcode 2.5. If it's good, I'll go to > work on more. > > The build slave name is "parc-tiger-1". As Antoine noted the test failures are unexpected, could you check if the tests pass if you do the build and testrun manually? IMHO it would be better to do a framework build for at least some of the OSX buildbots because that's what is in the binary installer for OSX. Ronald smime.p7s Description: S/MIME cryptographic 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/archive%40mail-archive.com
Re: [Python-Dev] please take a look at buildbot result [was: Broken link to download (Mac OS X)]
Ronald Oussoren wrote: > As Antoine noted the test failures are unexpected, could you check if > the tests pass if you do the build and testrun manually? I'll have to fiddle with where it "is" on our network to do that. I'll take it down and move it to different subnet. What about this error? /bin/sh: line 1: pybuildbot.identify: command not found It looks like a configuration issue, or maybe a bug in pybuildbot. What about readline? Darwin doesn't have it (or rather, it has a different one). Why is that 'skip' unexpected? > IMHO it would be better to do a framework build for at least some of > the OSX buildbots because that's what is in the binary installer for > OSX. Yes, that sounds good to me, too. But how do we make that a standard test so that appropriately enabled buildbot slaves will do it automatically? Something that gets configured in the build master? Bill ___ 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/archive%40mail-archive.com
Re: [Python-Dev] please take a look at buildbot result [was: Broken link to download (Mac OS X)]
On 29/04/2010 16:13, Ronald Oussoren wrote:
On 29 Apr, 2010, at 16:39, Bill Janssen wrote:
Ned Deily wrote:
In article<19399.11323.946604.992...@montanaro.dyndns.org>,
s...@pobox.com wrote:
Ned> Any idea what type of machine it is and where it is currently
Ned> located?
I seem to recall it is/was a G4 XServe. My guess as to location would be at
xs4all.nl.
If it were working that could be of use. It would not be able to run OS
X 10.6 but having a 10.5 system PPC system as a buildbot would certainly
be useful; it should be fine for the default installer configuration
builds. (Alas, I don't expect to be anywhere in the vicinity in the
foreseeable future.)
I've identified 4 G4/G5 machines at PARC I can set up as build slaves
on either Tiger or Leopard, and the first one of those is up (G4/Tiger)
and running. Can someone (Ned?) take a look at the output and see if
the errors are currently expected, or if I need to do more
config/install work? I'm using Xcode 2.5. If it's good, I'll go to
work on more.
The build slave name is "parc-tiger-1".
As Antoine noted the test failures are unexpected, could you check if the tests
pass if you do the build and testrun manually?
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.
Michael
IMHO it would be better to do a framework build for at least some of the OSX
buildbots because that's what is in the binary installer for OSX.
Ronald
___
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/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
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] The Meaning of Resolotion (Re: bug tracker permissions request)
On 4/27/2010 5:14 PM, "Martin v. Löwis" wrote: The page doesn't document the Resolution or Status fields. The resolutions are the same as the ones on SourceForge. They no longer have to be (see below). In any case, the meanings should be independently documented here for people not currently using SF. You only have resolutions on closed issues, Only for 'closed' or also for 'pending' and 'languishing'? If pending were implemented to mean 'auto close in x days', then Resolution would need to be set when Status is set to 'pending'. 'Languishing' is new (its first use was two months ago). Is it a form of 'open' or of 'closed'? > and they explain why an issue was closed. This needs to be explicitly stated in the doc if you want it followed. In response to my repeating this on the tracker, bugs.python.org/issue7511 R. David Murray said (in part) "Some committers have been using 'resolution: accepted' as a way to mark issues that are definitely going to be fixed/enhancement added." This is a different and therefore confusing use of the field and strikes me as mostly redundant with the newer Stage field with a value of Needs patch or later. If any specific one is unclear in that context, please be more specific. Tarek responded to David's full message "Yes I used 'accepted' to mark this issue as something I am working on." This usage overlaps with 'assigned to'. And he continued "I am confused about the resolution flag, I think it is a bit overlapping with the status flag, and overcomplex." This *is* overlap Resolution set means Status not open. I agree with the over-complex part. There was a discussion here some time ago on the fine distinctions, but I am again fuzzy on 'accepted' versus 'fixed', 'later' versus 'postponed', and 'invalid' versus 'works for me'. I have no idea when 'remind' would be used (it has only been used 8 times). For languishing, click on the label "Status" left of the field. I never noticed this. there are also pop-up boxed for Stage, Priority, and Keywords. There should also be a pop-up for Resolution. And the pop-up tables should also be in the doc. For the Keywords field, the page only documents the "easy" keyword. There are all documented in the pop-up box, which should be duplicated in the doc. Terry Jan Reedy ___ 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/archive%40mail-archive.com
Re: [Python-Dev] please take a look at buildbot result [was: Broken link to download (Mac OS X)]
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 And here's the results with "make test": 342 tests OK. 6 tests failed: test_argparse test_grp test_posix test_pwd test_socket_ssl test_urllib2_localnet 37 tests skipped: test_aepack test_al test_applesingle test_bsddb test_bsddb3 test_cd test_cl test_codecmaps_cn test_codecmaps_hk test_codecmaps_jp test_codecmaps_kr test_codecmaps_tw test_curses test_epoll test_gdb test_gdbm test_gl test_imgfile test_largefile test_linuxaudiodev test_macos test_macostools test_ossaudiodev test_readline test_scriptpackages test_smtpnet test_socketserver test_startfile test_sunaudiodev test_timeout test_tk test_ttk_guionly test_urllib2net test_urllibnet test_winreg test_winsound test_zipfile64 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. Bill ___ 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/archive%40mail-archive.com
Re: [Python-Dev] please take a look at buildbot result [was: Broken link to download (Mac OS X)]
On Thu, 29 Apr 2010 11:28:47 -0700, Bill Janssen wrote: > 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. I think someone fixed readline to work with Darwin's readline, at least in theory. -- R. David Murray www.bitdance.com ___ 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/archive%40mail-archive.com
[Python-Dev] array matching
Hey guys, I am sorry if this is not the right list to post some questions. I have a simple question please and would appreciate some answers as I am new to Python. I have 2 D array: test = [[A,1],[B,2],[A,3][B,4]] I want to arrang this array in different arrays so each one will have what is attached to. For example I want the output: A =[1,3] and B=[2,4] Thanks, Bill ___ 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/archive%40mail-archive.com
Re: [Python-Dev] array matching
Hello. We'are sorry but we cannot help you. This mailing list is to work on developing Python (fixing bugs and adding new features to Python itself); if you're having problems using Python, please find another forum. Probably python-list (comp.lang.python) news group/mailing list is the best place. See http://www.python.org/community/lists/ for other lists/news groups/fora. Thank you for understanding. On Thu, Apr 29, 2010 at 10:58:15AM -0700, Bill Jordan wrote: > I am sorry if this is not the right list to post some questions. I have a > simple question please and would appreciate some answers as I am new to > Python. > > I have 2 D array: test = [[A,1],[B,2],[A,3][B,4]] > I want to arrang this array in different arrays so each one will have what is > attached to. For example I want the output: > > A =[1,3] and B=[2,4] > > Thanks, > Bill Oleg. -- Oleg Broytmanhttp://phd.pp.ru/p...@phd.pp.ru Programmers don't die, they just GOSUB without RETURN. ___ 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/archive%40mail-archive.com
Re: [Python-Dev] array matching
On 4/29/2010 1:58 PM, Bill Jordan wrote: I am sorry if this is not the right list to post some questions. You cross-posted to 4. Not good as answers will go to all 4 if responders are not careful. Gmane.comp.python.devel is only for the development of the next versions of CPython and mainly for developers. Please to not send general questions here. Terry Jan Reedy ___ 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/archive%40mail-archive.com
Re: [Python-Dev] The Meaning of Resolotion (Re: bug tracker permissions request)
On Thu, 29 Apr 2010 14:11:57 -0400, Terry Reedy wrote: > On 4/27/2010 5:14 PM, "Martin v. Loewis" wrote: > > You only have resolutions on closed issues, > > Only for 'closed' or also for 'pending' and 'languishing'? > If pending were implemented to mean 'auto close in x days', then > Resolution would need to be set when Status is set to 'pending'. Definitely. Resolution should always be set for Pending, IMO. > 'Languishing' is new (its first use was two months ago). Is it a form of > 'open' or of 'closed'? Open. > > and they explain why an issue was closed. > > This needs to be explicitly stated in the doc if you want it followed. > > In response to my repeating this on the tracker, > bugs.python.org/issue7511 > R. David Murray said (in part) > "Some committers have been using 'resolution: accepted' as a way to mark > issues that are definitely going to be fixed/enhancement added." > > This is a different and therefore confusing use of the field and strikes > me as mostly redundant with the newer Stage field with a value of Needs > patch or later. Well, where it gets ambiguous is that the stage can get set to unit test or patch needed because that's what stage the bug report is in, without anyone having made a decision as to whether or not the patch will actually get applied if the patch is completed. So some way of indicating that the bug/enhancement is 'accepted' and will be applied as soon as it passes muster seems like a good idea, as opposed to issues where the evolution of the patch is part of the decision making process as to whether to accept it or not. I agree that having that be the 'resolution' field is logically and pedagogically incorrect ;) I've made a proposal (discussed with some of the other triage people) that would clarify this (and perhaps ultimately lead to the elimination of the stage field, although I don't mention that idea on the wiki), at: http://wiki.python.org/moin/DesiredTrackerFeatures I believe Ezio will be looking at this this summer. > > If any specific one is unclear in that context, please be more specific. [...] > over-complex part. There was a discussion here some time ago on the fine > distinctions, but I am again fuzzy on 'accepted' versus 'fixed', 'later' > versus 'postponed', and 'invalid' versus 'works for me'. I have no idea > when 'remind' would be used (it has only been used 8 times). In my mind some of these are clear (at least when using the field as it is labeled: for 'resolution'), but clearly the docs need help. 'accepted' would be for an enhancement (committing an enhancement doesn't 'fix' anything), while 'fixed' means the bug no longer exists. 'invalid' means that the bug report is just wrong, it's not a bug, while 'works for me' usually means that we can't reproduce the problem. I agree that some bugs that get closed 'works for me' really should be closed using another resolution. I doubt the reverse is true. I suspect 'works for me' gets used sometimes instead of invalid because the closer isn't sure that everyone on the dev teams shares their opinion that the bug is invalid or; more often, in cases where "won't fix" would be more appropriate. 'Accepted' and 'fixed' could be replaced by the single resolution 'committed'. That will eliminate the ambiguity of using 'accepted' as something other than a resolution. 'Works for me' should probably be dropped and replaced by "can't reproduce". 'later', 'remind', and 'postponed' all seem too close to be useful distinctions, and all seem pretty much equivalent to 'languishing'. IMO only one of the four should be kept. I prefer 'languishing' because it shows up as an issue count in the weekly summary, and it seems to me to me that this marking for an issue is more of a status than a resolution. (That is, 'later', 'remind', and 'postponed' are *not* resolutions, they are procrastinations, which 'languishing' makes explicit.) > > For languishing, click on the label "Status" left of the field. > > and Keywords. There should also be a pop-up for Resolution. > And the pop-up tables should also be in the doc. It would be great if you would open an issue for these suggestions in the meta-tracker, so that they don't get lost. If there is no objection to the resolution changes I suggest above, I can do those. I believe issues closed with those resolutions would keep them, and that there is a way for someone to mine for them if they ever wanted to go through and reevaluate them. I could optionally change all 'accepted' and 'fixed' into 'committed' since that change is pretty unambiguous, but the others I think should just be left unchanged on the existing issues unless someone feels moved to change a given issue by hand. This would leave us with the following list of resolutions: committed out of date duplicate can't reproduce invalid won't fix rejected The only remaining redundancy is "won't fix" versus "rejected", but I can't think of single word tha
Re: [Python-Dev] please take a look at buildbot result [w as: Broken link to download (Mac OS X)]
R. David Murray bitdance.com> writes: > > On Thu, 29 Apr 2010 11:28:47 -0700, Bill Janssen wrote: > > 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. > > I think someone fixed readline to work with Darwin's readline, at > least in theory. The machine is likely lacking the readline development headers. In any case, please don't focus on the skipped tests. What's important is the failed tests. Bill, Michael, it would be nice if you could investigate a bit more on these failures. Regards Antoine. ___ 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/archive%40mail-archive.com
Re: [Python-Dev] please take a look at buildbot result
Bill Janssen writes: >Ronald Oussoren wrote: >> As Antoine noted the test failures are unexpected, could you check if >> the tests pass if you do the build and testrun manually? > What about readline? Darwin doesn't have it (or rather, it has a > different one). Why is that 'skip' unexpected? For what it's worth, for the libraries, I used the build-installer script to build the same versions of libraries that it uses for the binary installer, and installed them in /usr/local for my buildbot to use, until there's enough time to have the buildbot build such local libraries within its own tree. That at least matches up the external dependencies for buildbot builds with that used by the eventual binary installer. For my buildbot, generally the only unexpected skips are for test_bsddb185 (which feels right to me - I don't have that version of the library, nor do I think has the binary installer) and test_ioctl (which I have no idea on yet). >> IMHO it would be better to do a framework build for at least some of >> the OSX buildbots because that's what is in the binary installer for >> OSX. > > Yes, that sounds good to me, too. But how do we make that a standard > test so that appropriately enabled buildbot slaves will do it > automatically? Something that gets configured in the build master? This came up in the earlier discussion, and while I do still think that's a better long term approach, I suspect that with respect to test coverage and code generation the non-framework build for the interpreter is a fair representation for testing. I suspect much of this is just a builder change on the master (to use the right Makefile targets for generating the framework build), but just given experience to date getting the binary installer building under buildbot, there may be some unexpected environmental stuff. Ideally we'd work up a way to do a universal framework build (though I'm not sure what if any extra support may be needed to have the system use the framework if not installed in a standard location), and then for full testing, maybe even use the makefile target that tests both the Intel and PPC path (the latter via Rosetta on an Intel system). What I'm not sure about at the moment is how much different in terms of testing such a setup might be (if, for example, any extra work is needed to be able to test a framework build while still local in the buildbot tree and not in a normal framework location), so how much energy is worth putting into it, especially if that might use resource among those able to resolve some of the open code issues. For my part, if there's free cycles I'd personally rather address the external library issue first, as opposed to the framework build stuff, since that feels more fragile to me (in terms of the buildbot environment for the Mac) at the moment. Over the past few weeks I'm also fairly sure that I'm finding stranded python test processes (not too dissimilar as on the Windows buildbots) that are bogging down the buildbot and thus more detrimental to ongoing buildbot operation than the lack of framework builds, so there may be other unknown issues more valuable to hit as we get more experience. -- David ___ 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/archive%40mail-archive.com
Re: [Python-Dev] The Meaning of Resolotion (Re: bug tracker permissions request)
R. David Murray wrote: > On Thu, 29 Apr 2010 14:11:57 -0400, Terry Reedy wrote: >> On 4/27/2010 5:14 PM, "Martin v. Loewis" wrote: >>> You only have resolutions on closed issues, >> Only for 'closed' or also for 'pending' and 'languishing'? >> If pending were implemented to mean 'auto close in x days', then >> Resolution would need to be set when Status is set to 'pending'. > > Definitely. Resolution should always be set for Pending, IMO. Note that I'll occasionally use "pending" to mean "committed to at least one branch, still need to port/block remaining branches". (e.g. I did it this week, since 2.7b2 was higher priority than the other branches which don't have near term binary releases coming up). I've seen others use it that way as well. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia --- ___ 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/archive%40mail-archive.com
Re: [Python-Dev] The Meaning of Resolotion (Re: bug tracker permissions request)
>> You only have resolutions on closed issues, > > Only for 'closed' or also for 'pending' and 'languishing'? Probably for all of them. I don't understand languishing, though (neither as an English word, nor as a status). > 'Languishing' is new (its first use was two months ago). Is it a form of > 'open' or of 'closed'? I have no idea. > This needs to be explicitly stated in the doc if you want it followed. I personally don't - I don't think it matters that much to have a resolution field if you also post a message explaining why the issue was closed. I'm just reporting what it was meant for originally. > I never noticed this. there are also pop-up boxed for Stage, Priority, > and Keywords. There should also be a pop-up for Resolution. > > And the pop-up tables should also be in the doc. Contributions welcome. Regards, Martin ___ 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/archive%40mail-archive.com
Re: [Python-Dev] The Meaning of Resolotion (Re: bug tracker permissions request)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin v. Löwis wrote: >>> You only have resolutions on closed issues, >> Only for 'closed' or also for 'pending' and 'languishing'? > > Probably for all of them. I don't understand languishing, though > (neither as an English word, nor as a status). > >> 'Languishing' is new (its first use was two months ago). Is it a form of >> 'open' or of 'closed'? > > I have no idea. Open, definitely: it implies "suffering due to neglect", combining senses 2 and 5 from this page: http://en.wiktionary.org/wiki/languish Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvaAxUACgkQ+gerLs4ltQ6lIwCePWePnXRfHbvRcx3Ih6rV7AhQ qiYAn2V5yR/PjIb+WSr/ILhO5p3WGHoO =XWHS -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/archive%40mail-archive.com
Re: [Python-Dev] please take a look at buildbot result [w as: Broken link to download (Mac OS X)]
Antoine Pitrou wrote: > R. David Murray bitdance.com> writes: > > > > On Thu, 29 Apr 2010 11:28:47 -0700, Bill Janssen wrote: > > > 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. > > > > I think someone fixed readline to work with Darwin's readline, at > > least in theory. > > The machine is likely lacking the readline development headers. > In any case, please don't focus on the skipped tests. What's important is the > failed tests. > Bill, Michael, it would be nice if you could investigate a bit more on these > failures. Well, test_grp test is failing because it assumes that group IDs are unique, which is not guaranteed by getgrent(). And apparently not true at PARC. test_posix fails on some group-related thing, too: the use of initgroups(), which is supposed to fail, succeeds. test_pwd fails because the fake uid chosen for one test is a real UID for a PARC user. So these are really problems with the test being based on an insufficiently general model of the real world. Bill ___ 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/archive%40mail-archive.com
Re: [Python-Dev] [melbourne-pug] array matching
You could use dictionary of lists
test = {
A: [1, 3],
B: [2, 4]
}
print test[A]
[1, 3]
test[A].append(5)
print test[A]
[1, 3, 5]
Cheers,
Fil
_
From: melbourne-pug-bounces+filipz=3g.nec.com...@python.org
[mailto:melbourne-pug-bounces+filipz=3g.nec.com...@python.org] On Behalf Of
Bill Jordan
Sent: Friday, 30 April 2010 3:58 AM
To: python-dev@python.org; python-l...@python.org; bangpyp...@python.org;
melbourne-...@python.org; portl...@python.org
Subject: [melbourne-pug] array matching
Hey guys,
I am sorry if this is not the right list to post some questions. I have a
simple question please and would appreciate some answers as I am new to
Python.
I have 2 D array: test = [[A,1],[B,2],[A,3][B,4]]
I want to arrang this array in different arrays so each one will have what
is attached to. For example I want the output:
A =[1,3] and B=[2,4]
Thanks,
Bill
___
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/archive%40mail-archive.com
Re: [Python-Dev] The Meaning of Resolotion (Re: bug tracker permissions request)
On Fri, 30 Apr 2010 07:17:02 +1000, Nick Coghlan wrote: > R. David Murray wrote: > > On Thu, 29 Apr 2010 14:11:57 -0400, Terry Reedy wrote: > >> On 4/27/2010 5:14 PM, "Martin v. Loewis" wrote: > >>> You only have resolutions on closed issues, > >> Only for 'closed' or also for 'pending' and 'languishing'? > >> If pending were implemented to mean 'auto close in x days', then > >> Resolution would need to be set when Status is set to 'pending'. > > > > Definitely. Resolution should always be set for Pending, IMO. > > Note that I'll occasionally use "pending" to mean "committed to at least > one branch, still need to port/block remaining branches". (e.g. I did it > this week, since 2.7b2 was higher priority than the other branches which > don't have near term binary releases coming up). > > I've seen others use it that way as well. Yes, I have noticed that several people do this. This will stop working if we implement autoclose. Other people just leave the issue open and change the targeted versions instead. -- R. David Murray www.bitdance.com ___ 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/archive%40mail-archive.com
Re: [Python-Dev] please take a look at buildbot result [w as: Broken link to download (Mac OS X)]
On Thu, 29 Apr 2010 17:27:44 -0700, Bill Janssen wrote: > Well, test_grp test is failing because it assumes that group IDs are > unique, which is not guaranteed by getgrent(). And apparently not true > at PARC. > > test_posix fails on some group-related thing, too: the use of > initgroups(), which is supposed to fail, succeeds. > > test_pwd fails because the fake uid chosen for one test is a real UID > for a PARC user. > > So these are really problems with the test being based on an > insufficiently general model of the real world. Could you file bugs for these, please? The first and last others should be able to replicate easily; the middle one will probably require your help on the machine in question to debug. -- R. David Murray www.bitdance.com ___ 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/archive%40mail-archive.com
Re: [Python-Dev] please take a look at buildbot result [was: Broken link to download (Mac OS X)]
On 29 Apr, 2010, at 20:47, R. David Murray wrote: > On Thu, 29 Apr 2010 11:28:47 -0700, Bill Janssen wrote: >> 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. > > I think someone fixed readline to work with Darwin's readline, at > least in theory. The readline extension works with Darwin's readline emulation, but only when the deployment target is 10.5 or later. Ronald smime.p7s Description: S/MIME cryptographic 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/archive%40mail-archive.com
