- 23 Jan, 2003 2 commits
-
-
Guido van Rossum authored
it is already absolute; there may be a good reason.
-
Guido van Rossum authored
-
- 22 Jan, 2003 8 commits
-
-
Guido van Rossum authored
-
Guido van Rossum authored
Add an <eventlog> section to the runner schema. Some comment and docstring tweakage.
-
Fred Drake authored
types.
-
Guido van Rossum authored
Add socket-name to runner conf template. Check that the port isn't in use already.
-
Guido van Rossum authored
-
Guido van Rossum authored
-
Barry Warsaw authored
-
Chris Withers authored
-
- 21 Jan, 2003 3 commits
-
-
Guido van Rossum authored
-
Barry Warsaw authored
acts more like what happens when you commit new object revisions using the higher level interface.
-
Barry Warsaw authored
-
- 20 Jan, 2003 14 commits
-
-
Fred Drake authored
- make it easier for an admin to configure logging levels (by making the defaults more sane) - refactor the tests a little, in preparation for more tests
-
Fred Drake authored
- remove methods that aren't needed - rename "resolved" to "instance" for readability
-
Fred Drake authored
-
Fred Drake authored
- de-tabify everything
-
Guido van Rossum authored
-
Guido van Rossum authored
_deadline to None, to prevent reporting the same timeout more than once. Added a helpful comment too. :-)
-
Barry Warsaw authored
intent according to the comment.
-
Guido van Rossum authored
-
Guido van Rossum authored
- Get rid of _lock() and _unlock(); _lock() is inlined, and so is _unlock(), after factoring out some common code at the end of tpc_begin() and tpc_end(). - In the refactored _unlock() code, only call self.timeout.end() if self.locked was actually set. In the TimeoutThread class: - Add some comments. - Add some assertions. - Get rid of the stop() method; we're a daemon thread so we'll be killed anyway; close_server() is only used from the test suite. - Switch from using a lock + an event to a condition variable. Be religious about doing stuff only while holding the lock. - Inline the timeout() function; it shouldn't reacquire the lock anyway. --Guido & Jeremy
-
Barry Warsaw authored
earlier in the loop. Basically, once we've got a tid from the transaction record, we check it against our stop tid, and we check the status looking for a 'c' flag.
-
Barry Warsaw authored
the middle of a transaction. This test isn't totally helpful in its own right, but run it with logging and you'll see the bogus warning (before the fix is applied).
-
Florent Guillaume authored
Fixed to correctly munge sys.path.
-
Guido van Rossum authored
that we can get distutils install to munge the #! line to insert the proper Python executable file name. (/usr/local/bin/python would work too, but may not be the Python version that you intended to use, so IMO it's better to require that you use an explicit Python interpreter when invoking the scripts before they are installed.
-
Fred Drake authored
-
- 18 Jan, 2003 2 commits
-
-
Guido van Rossum authored
runzeo.py lives -- that didn't work when runzeo.py is installed in /usr/local/bin.
-
Guido van Rossum authored
-
- 17 Jan, 2003 11 commits
-
-
Fred Drake authored
-
Fred Drake authored
activities these days.
-
Fred Drake authored
-
Fred Drake authored
-
Jeremy Hylton authored
-
Jeremy Hylton authored
-
Fred Drake authored
-
Jeremy Hylton authored
-
Guido van Rossum authored
-
Fred Drake authored
-
Fred Drake authored
-