First quarter 2010 Archives by author

• Messages sorted by: [ thread ] [ subject ] [ date ]
• More info on this list...

Starting: Fri Jan 1 22:28:49 CET 2010
Ending: Sun Feb 7 17:44:56 CET 2010
Messages: 36

• [execnet-commit] execnet commit ad1480851bf7: skip tests if it's not my account and there are not remote specs given indicating that we have a working ssh setup   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 6a3d4508d389: fix typo and bug on windows/python2.4   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 58cb2448414f: add to changelog, bump version   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 349c5987d135: fix GC sensitive compare   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 239d35261f4b: use newer apipkg   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit bb91c389fc3c: actually this check deals with a race-condition   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 8a7228ab86d3: always skip remote tests if not ssh specs given   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 6fa3e72d7a74: update apipkg   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 80164354090f: fix some doc issues (thanks thm and ronny), add ssh_fileserver example   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 9860c45a5adf: refine termination to a) react on EOFErrors as if GATEWAY_TERMINATE was sent explicitely b) have gateway termination try harder to interrupt execution on slaves.   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit fe49fd8cb655: popen gateways already re-use an existing installation   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 8d00cbdaa210: normalize a test with a too small timeout   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 773d50c557aa: going for 1.0.3   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 7614236c59e9: make gateway setup scope configurable for test runs   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 8481c6848eb8: report some extra information on execnet test runs   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 2444a6d0b235: make RemoteError not derive from EOFError to better distinguish error cases.   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 6673ab104a64: fix an un-nerving issue mostly related to jython - reading from files   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 1b755541dda9: fix python3 issue   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 18fd6228a2ea: make RemoteError and TimeoutError available directly, streamline changelog   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit f6ca92a5fee1: now that keyboardinterrupts are send from the receiver thread to the execution one, we should better let it pass through and not care anymore at process exit.   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit d1e4ec113bfa: send a special interrupt-text - another try to prevent shutdown from some racy messages.   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit bd0553b68265: more info   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 1222307f5014: try to have finalization code survive interpreter-shutdown and globals being set to None in particular   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 4112e1d76da6: fixate new doc version   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 5d74dad7f425: generally don't warn about keyboard-interrupted-messages   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit ca2fc9afbbff: Added tag 1.0.3 for changeset 5d74dad7f425   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit df0c1624a2f4: try harder to avoid bogus tracebacks, aim at execnet-1.0.4   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit e479c0849fce: making trace "global-None" safe as well and striking some duplicate tests   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 534f61972976: revert back to old tracing, rather simplify by trying less hard to keep tracing when globals are None during shutdown, cleanup tests   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 88d4464d2afb: fix doc-tagging, Added tag 1.0.4 for changeset 534f61972976   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit a1442c86ae53: fix glitch in example (thanks xa)   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit a5590cbab71b: just silence shutdown related exceptions at receiver-thread end (sigh)   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 3fc00577c03e: add a "setup.py test" target which runs py.test   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 7094cc4bfb7e: fix docstring, more carefullness during receiverthread finalization   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 9e7b55db59f9: prepare a 1.0.5 release, try to finalize interp-shutdown issues   commits-noreply at bitbucket.org
• [execnet-commit] execnet commit 6cc53b6a86e1: Added tag 1.0.5 for changeset 9e7b55db59f9   commits-noreply at bitbucket.org

Last message date: Sun Feb 7 17:44:56 CET 2010
Archived on: Sun Feb 7 17:45:27 CET 2010

• Messages sorted by: [ thread ] [ subject ] [ date ]
• More info on this list...