1. 22 Jun, 2005 1 commit
    • Tim Peters's avatar
      Merge rev 30894 from 3.4 branch. · c43d7912
      Tim Peters authored
      Largely rewritten.
      
      remove_loop_callback():  There were two definitions of this function.
      Deleted one, changed the other to use enumerate().
      
      poll():  This was trying to repair a bug in Python 2.2's asyncore.poll().
      2.2 is no longer supported, so removed this poll().
      
      _start_loop(), _stop_loop():  Removed; functionality folded into
      reworked loop().
      
      loop():  The signature of asyncore.loop() changed in 2.4, but this
      still had "the old" signature.  Instead of sniffing the signature
      of the Python in use, this does a saner thing:  the original
      asyncore.loop is captured, and called from the body of this loop().
      That way, (A) we don't care what asyncore.loop's signature is; and,
      (B) we still call the original Python code, so debugging prints and
      breakpoints (etc) stuffed into Python's asyncore no longer "vanish
      by magic" when ZEO is used.
      c43d7912
  2. 21 Jun, 2005 1 commit
    • Tim Peters's avatar
      Merge rev 30877 from 3.4 branch. · f0bb9db5
      Tim Peters authored
      Massive refactoring, to move the bulk of the trigger code into
      an OS-indepedent base class.
      
      __repr__:  Use the postive_id function to embed the machine address.
      Addresses with the high bit set trigger warnings before Python 2.4,
      and come out as negative numbers in 2.4+.
      
      Windows trigger.__init__:  Don't make 50 guesses at a port number
      to use, let Windows pick an available port for us.  Also documented
      the baffling single-thread socket setup dance, which took an hour to
      reverse-engineer (in large part because it used a bare "except" w/ no
      clue as to why).
      f0bb9db5
  3. 17 Jun, 2005 2 commits
    • Jim Fulton's avatar
      Updated release numbers. · 1477c3c9
      Jim Fulton authored
      1477c3c9
    • Jim Fulton's avatar
      We check for implicitly adding objects by looking for "new" objects · 316ea575
      Jim Fulton authored
      reachable from multiple connections.  Previously, we thought that we
      could limit the time that an object was new to a single savepoint, but
      that didn't work because savepoints of different connections are too
      independent.   Now an object is considered new for the full extent of
      the transaction in which it was created.
      
      Made it possible to use connection add methods to explicitly control
      the database an object is added too.
      316ea575
  4. 16 Jun, 2005 8 commits
  5. 15 Jun, 2005 1 commit
  6. 14 Jun, 2005 1 commit
  7. 10 Jun, 2005 2 commits
  8. 09 Jun, 2005 8 commits
  9. 06 Jun, 2005 4 commits
  10. 03 Jun, 2005 1 commit
  11. 02 Jun, 2005 4 commits
  12. 31 May, 2005 2 commits
  13. 27 May, 2005 3 commits
  14. 26 May, 2005 1 commit
    • Tim Peters's avatar
      Merge rev 30518 from 3.4 branch. · 5c34be65
      Tim Peters authored
      Change test.py to use zope.testing.testrunner, and update the
      latter to Jim's development version.  Hardest part turned out
      to be teaching ZODB's setup.py how to "build" this version of
      zope.testing (it has a lot of packages in a test directory,
      where the latter is not itself a package).
      
      Incidentally repaired an oversight in building zope.interface
      too.
      5c34be65
  15. 20 May, 2005 1 commit