1. 04 Agu, 2016 1 kayıt (commit)
  2. 26 May, 2016 1 kayıt (commit)
  3. 09 May, 2016 1 kayıt (commit)
  4. 14 Kas, 2015 1 kayıt (commit)
  5. 11 Eki, 2015 1 kayıt (commit)
  6. 06 Eki, 2015 1 kayıt (commit)
  7. 04 Eki, 2014 1 kayıt (commit)
  8. 21 Eyl, 2014 1 kayıt (commit)
  9. 02 Eyl, 2014 1 kayıt (commit)
  10. 29 Agu, 2014 1 kayıt (commit)
  11. 26 May, 2014 1 kayıt (commit)
  12. 20 Mar, 2014 1 kayıt (commit)
  13. 17 Mar, 2014 1 kayıt (commit)
  14. 26 Eki, 2013 3 kayıt (commit)
  15. 13 Eki, 2013 1 kayıt (commit)
  16. 09 Eki, 2013 1 kayıt (commit)
  17. 09 Eyl, 2013 4 kayıt (commit)
  18. 08 Eyl, 2013 3 kayıt (commit)
    • Tim Peters's avatar
      Issue 18984: Remove ._stopped Event from Thread internals. · c363a23e
      Tim Peters yazdı
      The fix for issue 18808 left us checking two things to be sure a Thread
      was done:  an Event (._stopped) and a mutex (._tstate_lock).  Clumsy &
      brittle.  This patch removes the Event, leaving just a happy lock :-)
      
      The bulk of the patch removes two excruciating tests, which were
      verifying sanity of the internals of the ._stopped Event after a fork.
      Thanks to Antoine Pitrou for verifying that's the only real value
      these tests had.
      
      One consequence of moving from an Event to a mutex:  waiters (threads
      calling Thread.join()) used to block each on their own unique mutex
      (internal to the ._stopped event), but now all contend on the same
      mutex (._tstate_lock).  These approaches have different performance
      characteristics on different platforms.  I don't think it matters in
      this context.
      c363a23e
    • Antoine Pitrou's avatar
      Issue #18808 again: fix the after-fork logic for not-yet-started or already-stopped threads. · 5da7e795
      Antoine Pitrou yazdı
      (AFAICT, in theory, we must reset all the locks, not just those in use)
      5da7e795
    • Tim Peters's avatar
      Issue 18808: blind attempt to repair some buildbot failures. · 68d7f787
      Tim Peters yazdı
      test_is_alive_after_fork is failing on some old Linux kernels, but
      passing on all newer ones.  Since virtually anything can go wrong
      with locks when mixing threads with fork, replace the most likely
      cause with a redundant simple data member.
      68d7f787
  19. 07 Eyl, 2013 1 kayıt (commit)
  20. 04 Eyl, 2013 2 kayıt (commit)
  21. 30 Agu, 2013 1 kayıt (commit)
  22. 17 Agu, 2013 1 kayıt (commit)
  23. 04 Tem, 2013 1 kayıt (commit)
  24. 14 Haz, 2013 1 kayıt (commit)
  25. 22 Nis, 2013 1 kayıt (commit)
  26. 30 Mar, 2013 1 kayıt (commit)
  27. 21 Mar, 2013 1 kayıt (commit)
  28. 11 Mar, 2013 2 kayıt (commit)
  29. 10 Mar, 2013 1 kayıt (commit)
  30. 09 Mar, 2013 1 kayıt (commit)
  31. 10 Agu, 2012 1 kayıt (commit)