1. 07 Sep, 2008 4 commits
  2. 04 Sep, 2008 2 commits
  3. 01 Sep, 2008 1 commit
  4. 31 Aug, 2008 1 commit
  5. 23 Aug, 2008 1 commit
  6. 22 Aug, 2008 1 commit
  7. 20 Aug, 2008 3 commits
  8. 19 Aug, 2008 2 commits
  9. 18 Aug, 2008 1 commit
  10. 17 Aug, 2008 4 commits
  11. 14 Aug, 2008 1 commit
    • Hirokazu Yamamoto's avatar
      Issue #2065: VC6 related fix. · f0a41637
      Hirokazu Yamamoto authored
      - PC/VC6/_bsddb.dsp:
          removed '/nodefaultlib:"msvcrt"' to fix linker error.
      
      - PC/VC6/_msi.dsp:
          added new module support.
      
      - PC/VC6/_sqlite3.dsp:
          /D "MODULE_NAME=\"sqlite3\""
          caused extra leading space like
          #define MODULE_NAME " sqlite3"
          so uses
          /D MODULE_NAME=\"sqlite3\"
          instead.
      
      - PC/VC6/python.dsp:
          changed stack size to 2MB to avoid stack overflow on
          some tests.
      f0a41637
  12. 12 Aug, 2008 3 commits
  13. 11 Aug, 2008 1 commit
  14. 10 Aug, 2008 1 commit
  15. 04 Aug, 2008 4 commits
  16. 02 Aug, 2008 1 commit
  17. 31 Jul, 2008 1 commit
  18. 28 Jul, 2008 1 commit
    • Neal Norwitz's avatar
      Backport code from r65182: · 83ac0144
      Neal Norwitz authored
      Issue #2620: Overflow checking when allocating or reallocating memory
      was not always being done properly in some python types and extension
      modules.  PyMem_MALLOC, PyMem_REALLOC, PyMem_NEW and PyMem_RESIZE have
      all been updated to perform better checks and places in the code that
      would previously leak memory on the error path when such an allocation
      failed have been fixed.
      83ac0144
  19. 25 Jul, 2008 1 commit
  20. 16 Jul, 2008 2 commits
  21. 13 Jul, 2008 1 commit
  22. 06 Jul, 2008 1 commit
  23. 02 Jul, 2008 1 commit
  24. 01 Jul, 2008 1 commit
    • Amaury Forgeot d'Arc's avatar
      #Issue3088 in-progress: Race condition with instances of classes derived from threading.local: · b15bdf7f
      Amaury Forgeot d'Arc authored
      When a thread touches such an object for the first time, a new thread-local __dict__ is created,
      and the __init__ method is run.
      But a thread switch can occur here; if the other thread touches the same object, it installs another
      __dict__; when the first thread resumes, it updates the dictionary of the second...
      
      This is the deep cause of the failures in test_multiprocessing involving "managers" objects.
      
      Backport of r64601.
      b15bdf7f