1. 16 Apr, 2004 1 commit
  2. 15 Apr, 2004 12 commits
  3. 14 Apr, 2004 3 commits
  4. 13 Apr, 2004 10 commits
  5. 12 Apr, 2004 2 commits
  6. 09 Apr, 2004 8 commits
  7. 08 Apr, 2004 2 commits
  8. 06 Apr, 2004 2 commits
    • Tim Peters's avatar
      ZODB.utils grows a new function positive_id(), which returns the id() of · b0b7489e
      Tim Peters authored
      an object as a non-negative integer.  Code trying to pass addresses to
      an %x format uses positive_id(), and this avoids a Python FutureWarning
      about applying %x to negative ints.  The primary difference between this
      and the last stab is that positive_id() should work OK on 64-bit boxes
      too.  What we really want here is C's %p format code, but in Python we
      can't even reliably know the width of native addresses.
      b0b7489e
    • Tim Peters's avatar
      As part of int/long unification, Python 2.4 will start printing · 771d5748
      Tim Peters authored
      negative ints *as* negative ints when fed into %x formats.  Python 2.3
      still renders them as positive ints, but spews
      
      FutureWarning: %u/%o/%x/%X of negative int will return a signed string
                     in Python 2.4 and up
      
      to warn about the impending change.  Jim reported two instances of that
      warning when running the tests on a box where addresses happen to "be
      negative".  So make the addresses look positive instead (2.3 and 2.4
      treat those the same, so 2.3 doesn't warn about those).
      
      Problem:  it occurs to me now that I'm assuming addresses fit in 32
      bits here.
      771d5748