[Tim said]
> Over the last 12 hours, 4 tests started failing on Windows:
>
> 4 tests failed: test_descr test_future test_generators test_scope
>
> Would someone on Linux please confirm or deny it's not unique to
> Windows? I don't want to spend a lot of time tracking these down
> if the responsible parties see them on their boxes too.
But only in release mode. In a debug build, these pass. This strongly
suggests a change "somewhere" that accidentally relies on an uninitialized
value. Under the release build, I get oodles of bogus warnings related to
scope, like
../lib/test/test_scope.py:401: SyntaxWarning:
local name 'x' in 'f1' shadows use of 'x' as global in nested
scope 'f2'
so best guess is it's Jeremy's recent future-flag fiddling patches.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4