1. 19 Eyl, 2000 2 kayıt (commit)
    • Tim Peters's avatar
      Obscure marshal fixes: · e84b7403
      Tim Peters yazdı
          When reading a short, sign-extend on platforms where shorts are
          bigger than 16 bits.
          When reading a long, repair the unportable sign extension that was
          being done for 64-bit machines (it assumed that signed right shift
          sign-extends).
      e84b7403
    • Guido van Rossum's avatar
      Make better use of GNU Pth -- patch by Andy Dustman. · 9e8181b8
      Guido van Rossum yazdı
      I can't test this, so I'm just checking it in with blind faith in Andy.
      I've tested that it doesn't broeak a non-Pth build on Linux.
      
      Changes include:
      
      - There's a --with-pth configure option.
      
      - Instead of _GNU_PTH, we test for HAVE_PTH.
      
      - Better signal handling.
      
      - (The config.h.in file is regenerated in a slightly different order.)
      9e8181b8
  2. 18 Eyl, 2000 1 kayıt (commit)
  3. 16 Eyl, 2000 1 kayıt (commit)
  4. 15 Eyl, 2000 2 kayıt (commit)
  5. 08 Eyl, 2000 2 kayıt (commit)
  6. 05 Eyl, 2000 1 kayıt (commit)
  7. 04 Eyl, 2000 3 kayıt (commit)
  8. 03 Eyl, 2000 1 kayıt (commit)
  9. 02 Eyl, 2000 2 kayıt (commit)
    • Fredrik Lundh's avatar
      changed \x to consume exactly two hex digits. implements PEP-223 · 1fa0b895
      Fredrik Lundh yazdı
      for 8-bit strings.
      1fa0b895
    • Tim Peters's avatar
      PyInterpreterState_New is not thread-safe, and the recent fix to _PyPclose · 412f2460
      Tim Peters yazdı
      can cause it to get called by multiple threads simultaneously.
      
      Ditto for PyInterpreterState_Delete.
      
      Of the former, the docs say "The interpreter lock need not be held, but may
      be held if it is necessary to serialize calls to this function".  This
      kinda implies it both is and isn't thread-safe.
      
      Of the latter, the docs merely say "The interpreter lock need not be
      held.", and the clause about serializing is absent.
      
      I expect it was *believed* these are both thread-safe, and the bit about
      serializing via the global lock was meant as a permission rather than a
      caution.
      
      I also expect we've never seen a problem here because the Python core
      (prior to the _PyPclose fix) only calls these functions once per run.
      The Py_NewInterpreter subsystem exposed by the C API (but not used by
      Python itself) also calls them, but that subsystem appears to be very
      rarely used.
      
      Whatever, they're both thread-safe now.
      412f2460
  10. 01 Eyl, 2000 7 kayıt (commit)
  11. 31 Agu, 2000 4 kayıt (commit)
  12. 30 Agu, 2000 1 kayıt (commit)
  13. 29 Agu, 2000 1 kayıt (commit)
  14. 27 Agu, 2000 7 kayıt (commit)
  15. 25 Agu, 2000 2 kayıt (commit)
  16. 24 Agu, 2000 3 kayıt (commit)