-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 0.12.2 #25
Release 0.12.2 #25
Conversation
Anyone want to volunteer to review this? 😄 It's only like 20 lines. @mheilman @desilinguist @dmnapolitano @aoifecahill |
I didn't see anything obviously bad, but I'm not familiar enough with this code to really give a useful review. If nobody else is either, maybe you should sit down with one of us and explain the changes or something... ? |
Explaining it to at least one of you is a good idea. I don't know that I have time to meet about it this week, but here's a quick overview of how the whole GridMap system works. To run a function on a bunch of arguments using GridMap, you either use the
As a side note, I should also mention that the |
Since that explanation shouldn't get lost to time, I also put it on the wiki: https://github.com/EducationalTestingService/gridmap/wiki/How-GridMap-works-under-the-hood |
That's quite useful. Thanks! On Wed, Jan 8, 2014 at 10:17 AM, Dan Blanchard notifications@github.com
|
Just fixed a couple minor issues.
exception
is now the properly set as the cause of death when a job encounters an exception.qmaster
process caused by not cleaning up job info as recommended in the DRMAA Python documentation.session_id
inJobMonitor
toNone
to be more Pythonic, instead of -1 like it was before.