[Python-Dev] RE: Somebody stopped running tests?

Jeremy Hylton jeremy@zope.com
Mon, 13 Aug 2001 11:07:32 -0400 (EDT)

>>>>> "TP" == Tim Peters <tim_one@email.msn.com> writes:

  >> Over the last 12 hours, 4 tests started failing on Windows:
  >> 4 tests failed: test_descr test_future test_generators test_scope
  >> ...  But only in release mode.  In a debug build, these pass.
  >> This strongly suggests a change "somewhere" that accidentally
  >> relies on an uninitialized value.

  TP> And so it was.  "Fixed" in current CVS, but Jeremy needs to fix
  TP> it a right way.

Fixed now -- thought I'd mention it in the absence of any checkin
mail.  I had started down the path of removing all the
is-nested-scopes-enabled-or-not code, then decided to cleanup the
handling for future statements first.  I accidentally checked in one
of the former changes with the latter checkin.