Łukasz Langa <[email protected]> added the comment:
Unfortunately, exactly the same thing happens with
== CPython 3.3.0b1 (default:464c6a50b0ce, Jul 9 2012, 09:26:07) [GCC 4.2.1
Compatible Apple Clang 3.1 (tags/Apple/clang-318.0.61)]
== Darwin-11.4.0-x86_64-i386-64bit little-endian
==
/Users/ambv/Documents/Projekty/Python/cpython/py33/build/test_python_37987
Testing with flags: sys.flags(debug=0, inspect=0, interactive=0,
optimize=0, dont_write_bytecode=0, no_user_site=0, no_site=0,
ignore_environment=0, verbose=0, bytes_warning=0, quiet=0, hash_randomization=1)
What's interesting is that test_warnings itself works as advertised and it's
only Lib/unittest/test/_test_warnings.py that misbehaves.
On my friend's 10.7 machine everything runs fine with a little older Clang:
== CPython 3.3.0b1 (default, Jul 9 2012, 09:52:57) [GCC 4.2.1 Compatible
Apple Clang 3.0 (tags/Apple/clang-211.12)]
== Darwin-11.4.0-x86_64-i386-64bit little-endian
== /Users/sheep/dev/python/cpython-464c6a50b0ce/build/test_python_7695
Testing with flags: sys.flags(debug=0, inspect=0, interactive=0,
optimize=0, dont_write_bytecode=0, no_user_site=0, no_site=0,
ignore_environment=0, verbose=0, bytes_warning=0, quiet=0, hash_randomization=1)
Will investigate further.
----------
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue15279>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
