1. 07 Jun, 2001 4 commits
  2. 06 Jun, 2001 6 commits
  3. 05 Jun, 2001 5 commits
  4. 04 Jun, 2001 5 commits
  5. 03 Jun, 2001 5 commits
  6. 02 Jun, 2001 6 commits
  7. 01 Jun, 2001 1 commit
  8. 31 May, 2001 2 commits
  9. 30 May, 2001 3 commits
  10. 29 May, 2001 3 commits
    • Tim Peters's avatar
      This division test was too stringent in its accuracy expectations for · 0b76d3a8
      Tim Peters authored
      random inputs:  if you ran the test 100 times, you could expect it to
      report a bogus failure.  So loosened its expectations.
      Also changed the way failing tests are printed, so that when run under
      regrtest.py we get enough info to reproduce the failure.
      0b76d3a8
    • Tim Peters's avatar
      BadDictKey test: The output file expected "raising error" to be printed · 9a828d3c
      Tim Peters authored
      exactly once.  But the test code can't know that, as the number of times
      __cmp__ is called depends on internal details of the dict implementation.
      This is especially nasty because the __hash__ method returns the address
      of the class object, so the hash codes seen by the dict can vary across
      runs, causing the dict to use a different probe order across runs.  I
      just happened to see this test fail about 1 run in 7 today, but only
      under a release build and when passing -O to Python.  So, changed the test
      to be predictable across runs.
      9a828d3c
    • Fred Drake's avatar
      New solution to the "Someone stuck a colon in that filename!" problem: · 9a374186
      Fred Drake authored
      Allow colons in the labels used for internal references, but do not
      expose them when generating filename.
      9a374186