Brett Cannon e52c919d67 When trying to write new bytecode, importlib was not catching the IOError ... thrown if the file happened to be read-only to keep the failure silent. Fixes issue #7187. Thanks, Dave Malcolm for the report and analysis of the problem.		2009-11-07 23:55:05 +00:00
..
builtin	Move over to using assertRaises as a context manager for importlib tests.	2009-08-27 23:49:21 +00:00
extension	Move over to using assertRaises as a context manager for importlib tests.	2009-08-27 23:49:21 +00:00
frozen	Move over to using assertRaises as a context manager for importlib tests.	2009-08-27 23:49:21 +00:00
import_	Trying to import a submodule from another module and not a package was raising	2009-08-30 20:22:21 +00:00
source	When trying to write new bytecode, importlib was not catching the IOError	2009-11-07 23:55:05 +00:00
__init__.py	Importlib was using custom code to discover all test modules in importlib.test.	2009-07-15 04:08:33 +00:00
__main__.py	Provide module docstrings for the two main test drivers in importlib that	2009-08-30 08:39:57 +00:00
abc.py	Introduce importlib.abc. The module contains various ABCs related to imports	2009-03-09 03:35:50 +00:00
benchmark.py	Rework importlib benchmarks so that they measure number of executions within a	2009-09-03 20:45:21 +00:00
regrtest.py	Clarify why test_import is failing under importlib.	2009-08-30 23:41:40 +00:00
test_abc.py	Implement the PEP 302 protocol for get_filename() as	2009-07-20 04:23:48 +00:00
test_api.py	Move over to using assertRaises as a context manager for importlib tests.	2009-08-27 23:49:21 +00:00
test_util.py	convert old fail* assertions to assert*	2009-06-30 23:06:06 +00:00
util.py	Remove custom test-skipping code in importlib tests for unittest code.	2009-07-20 01:05:40 +00:00