1. 01 Eyl, 2000 1 kayıt (commit)
  2. 07 Agu, 2000 1 kayıt (commit)
  3. 22 Tem, 2000 1 kayıt (commit)
  4. 30 Haz, 2000 3 kayıt (commit)
    • Guido van Rossum's avatar
      Change copyright notice - 2nd try. · ffcc3813
      Guido van Rossum yazdı
      ffcc3813
    • Guido van Rossum's avatar
      Change copyright notice. · fd71b9e9
      Guido van Rossum yazdı
      fd71b9e9
    • Fred Drake's avatar
      Trent Mick <trentm@activestate.com>: · a44d353e
      Fred Drake yazdı
      The common technique for printing out a pointer has been to cast to a long
      and use the "%lx" printf modifier. This is incorrect on Win64 where casting
      to a long truncates the pointer. The "%p" formatter should be used instead.
      
      The problem as stated by Tim:
      > Unfortunately, the C committee refused to define what %p conversion "looks
      > like" -- they explicitly allowed it to be implementation-defined. Older
      > versions of Microsoft C even stuck a colon in the middle of the address (in
      > the days of segment+offset addressing)!
      
      The result is that the hex value of a pointer will maybe/maybe not have a 0x
      prepended to it.
      
      
      Notes on the patch:
      
      There are two main classes of changes:
      - in the various repr() functions that print out pointers
      - debugging printf's in the various thread_*.h files (these are why the
      patch is large)
      
      
      Closes SourceForge patch #100505.
      a44d353e
  5. 29 Haz, 2000 1 kayıt (commit)
  6. 28 Haz, 2000 1 kayıt (commit)
  7. 11 May, 2000 1 kayıt (commit)
    • Guido van Rossum's avatar
      Bill Tutt: · ede8c6ee
      Guido van Rossum yazdı
      Calling Sleep(0) for a spinlock can cause a priority inversion, adding
      comments to explain what's going on.
      ede8c6ee
  8. 05 May, 2000 1 kayıt (commit)
  9. 04 May, 2000 1 kayıt (commit)
    • Guido van Rossum's avatar
      Fast NonRecursiveMutex support by Yakov Markovitch, markovitch@iso.ru, · 706262bd
      Guido van Rossum yazdı
      who wrote:
      
      Here's the new version of thread_nt.h.  More particular, there is a
      new version of thread lock that uses kernel object (e.g. semaphore)
      only in case of contention; in other case it simply uses interlocked
      functions, which are faster by the order of magnitude.  It doesn't
      make much difference without threads present, but as soon as thread
      machinery initialised and (mostly) the interpreter global lock is on,
      difference becomes tremendous.  I've included a small script, which
      initialises threads and launches pystone.  With original thread_nt.h,
      Pystone results with initialised threads are twofold worse then w/o
      threads.  With the new version, only 10% worse.  I have used this
      patch for about 6 months (with threaded and non-threaded
      applications).  It works remarkably well (though I'd desperately
      prefer Python was free-threaded; I hope, it will soon).
      706262bd
  10. 20 Ock, 2000 1 kayıt (commit)
  11. 21 Ara, 1998 1 kayıt (commit)
  12. 14 Agu, 1997 1 kayıt (commit)
  13. 25 Eki, 1996 1 kayıt (commit)
  14. 08 Eki, 1996 1 kayıt (commit)
  15. 17 Ock, 1995 1 kayıt (commit)