Steve Dower added the comment: Looks like a test ordering issue. When test_imageop runs before test_py3kwarn, the warning has presumably already been shown once and so isn't triggered when the test is looking for it (compare build 3092 linked above with 3093, which passed).
I haven't looked any further into this, but I don't see how it's Windows specific. Adding the test coverage folks, since nobody seems to obviously own test_py3kwarn. ---------- components: +Tests nosy: +christian.heimes, giampaolo.rodola, ncoghlan _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23375> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
