An error occurred fetching the project authors.
  1. 13 Dec, 2002 1 commit
  2. 18 Nov, 2002 1 commit
  3. 12 Nov, 2002 1 commit
  4. 05 Nov, 2002 1 commit
  5. 01 Nov, 2002 1 commit
  6. 02 Oct, 2002 1 commit
    • Guido van Rossum's avatar
      Running the tests on Win98 would occasionally hang in the trigger · 4ff0c9ad
      Guido van Rossum authored
      __init__.  The hang was in the accept() call.  I don't understand
      exactly why, but I suspect it was because we were always reusing
      the same port when a trigger was closed and another opened right
      away.  Fixed this by cycling over ports [19950...19999].
      
      Also cleaned up the code somewhat.
      4ff0c9ad
  7. 16 Sep, 2002 2 commits
  8. 10 Sep, 2002 1 commit
  9. 30 Aug, 2002 1 commit
  10. 22 Aug, 2002 1 commit
    • Jeremy Hylton's avatar
      There were two copies trigger! · 63f03ca5
      Jeremy Hylton authored
      The one in ZEO/trigger.py was the good code, but we want it to live in
      ZEO/zrpc/trigger.py.  This checkin makes that change.
      
      The key checkin of ZEO/trigger.py had this checkin comment:
      Fix trigger close/__del__.
      
      The close() mechanism for an asyncore file_dispatcher is not safe to
      call multiple times.  It's calling os.close() on a file descriptor
      (int).  Guido observed that if you call close() twice, you could be in
      trouble:  1) First close() call closes FD 6.  2) Another bit of code
      opens a new file, getting FD 6.  3) Second close() call closes FD 6.
      Waah!  FD 6 is some other file.
      
      The workaround attempt here is to define a close() method on a trigger
      that only closes the file descriptors the first time.
      
      Also, make sure that both file descriptors are closed.  The previous
      version only closed the read-end of the pipe.
      63f03ca5
  11. 11 Jun, 2002 2 commits
  12. 04 Apr, 2002 1 commit
  13. 11 Feb, 2002 1 commit
  14. 02 Nov, 2001 1 commit
  15. 07 Sep, 2001 1 commit
  16. 11 Jan, 2001 1 commit