[issue7553] test_long_future is faulty

Mark Dickinson added the comment: Applied in r76984. Thanks! -- nosy: +mark.dickinson resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue7553] test_long_future is faulty

Florent Xicluna added the comment: Let me show the issue: ~ $ cat bar.py def apply_(func, args=(), kw={}): return func(*args, **kw) ~ $ cat foo.py from __future__ import division import bar def test(): assert eval('1/2') == .5 assert apply(eval, ('1/2',)) == .5 # This test yi

[issue7553] test_long_future is faulty

Benjamin Peterson added the comment: eval() inherits the flags of the module it is used in. -- nosy: +benjamin.peterson resolution: -> works for me status: open -> closed ___ Python tracker ___

[issue7553] test_long_future is faulty

Florent Xicluna added the comment: Removed 2.6 from the todolist. Not worth the effort. "with self.assertRaises(...):" construct is not supported in 2.6. -- versions: -Python 2.6 ___ Python tracker __

[issue7553] test_long_future is faulty

Changes by Florent Xicluna : -- stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue7553] test_long_future is faulty

Florent Xicluna added the comment: Patch which fixes the tests: call the "eval" in the module. -- keywords: +patch Added file: http://bugs.python.org/file15630/issue7553_test_long_future.diff ___ Python tracker ___

[issue7553] test_long_future is faulty

New submission from Florent Xicluna : This test do not test "true division" contrary to what is claimed. for zero in ["huge / 0", "huge / 0L", "mhuge / 0", "mhuge / 0L"]: self.assertRaises(ZeroDivisionError, eval, zero, namespace) Because it uses the module "unittest" to eval the ex