[issue5354] Add test.support.import_python_only

Nick Coghlan added the comment: New and improved version added to 2.7 as r71799 and 3.1 as r71801. Also cleaned up a few leftover references to test.test_support in the test package documentation. -- resolution: -> accepted status: open -> closed _

[issue5354] Add test.support.import_python_only

Nick Coghlan added the comment: The None->tuple check is a legacy of the original API where "None" actually meant to block "_name". I'll change it as you suggest. Your explanation as to why the test was failing in py3k makes sense. I think I will tidy that use case up a bit by adding a "fresh=(

[issue5354] Add test.support.import_python_only

Brett Cannon added the comment: On Sat, Apr 11, 2009 at 07:28, Nick Coghlan wrote: > > Nick Coghlan added the comment: > > Implemented for 2.7 in r71465 > Implemented for 3.1 in r7146 > Style nit: why the extra check for block_names being None to later set it to an empty tuple? Why not make

[issue5354] Add test.support.import_python_only

Nick Coghlan added the comment: Implemented for 2.7 in r71465 Implemented for 3.1 in r71469 Leaving issue open for the moment - the 3.1 test_warnings fails if I don't get a fresh copy of _warnings before running the unit tests. I want to figure out why that is necessary before closing the issue

[issue5354] Add test.support.import_python_only

Changes by Nick Coghlan : -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/opti

[issue5354] Add test.support.import_python_only

Nick Coghlan added the comment: Implemented for 2.7 in r71465 Implemented for 3.1 in r7146 Leaving issue open for the moment - the 3.1 test_warnings fails if I don't get a fresh copy of _warnings before running the unit tests. I want to figure out why that is necessary before closing the issue.

[issue5354] Add test.support.import_python_only

Nick Coghlan added the comment: Ended up going for a slightly more general name "import_fresh_module". Reason being, test_warnings *also* wanted a fresh version of the accelerated module along with a pure Python version - it seemed silly to only factor out half of the problem into a support func

[issue5354] Add test.support.import_python_only

Brett Cannon added the comment: On Mon, Feb 23, 2009 at 13:19, Nick Coghlan wrote: > > New submission from Nick Coghlan : > > Add test.support.import_python_only as per > http://mail.python.org/pipermail/python-dev/2009-February/086387.html > > Also add an equivalent to test.test_support in 2.

[issue5354] Add test.support.import_python_only

New submission from Nick Coghlan : Add test.support.import_python_only as per http://mail.python.org/pipermail/python-dev/2009-February/086387.html Also add an equivalent to test.test_support in 2.x (I haven't checked yet if importlib is available in 2.x, so the implementation may need to be a l