Rooba
/
cpython
mirror of https://github.com/python/cpython.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
cpython/Lib/importlib/NOTES

26 lines
764 B
Plaintext
Raw Normal View History

Add initial implementation of importlib. See the NOTES files for what is planned for the package. There are no docs yet, but they are coming once the API for the first new function, importlib.import_module() is finalized.
2009-01-18 00:24:28 +00:00
to do
/////
Finish implementing tests for importlib.machinery.PathFinder by testing that implicit hooks are handled properly.
2009-02-06 00:07:49 +00:00
* Public API left to expose (w/ docs!)
Add importlib.machinery with its first tenants, BuitinImporter and FrozenImporter. Docs forthcoming. I plan on all finders and loaders (and most likely hooks) to live in imoprtlib.machinery. Utility stuff will end up in importlib.util. Higher-level API stuff will stay on imoprtlib directly (e.g. import_module).
2009-01-22 22:43:07 +00:00
Introduce importlib.abc. The module contains various ABCs related to imports (mostly stuff specified by PEP 302). There are two ABCs, PyLoader and PyPycLoader, which help with implementing source and source/bytecode loaders by implementing load_module in terms of other methods. This removes a lot of gritty details loaders typically have to worry about.
2009-03-09 03:35:50 +00:00
+ abc.PyLoader.get_source
+ util.set_loader
Implement the more specific PEP 302 semantics for loaders and what happens upon load failure in relation to reloads. Also expose importlib.util.module_for_loader to handle all of the details of this along with making sure all current loaders behave nicely.
2009-02-17 02:45:03 +00:00
Introduce importlib.abc. The module contains various ABCs related to imports (mostly stuff specified by PEP 302). There are two ABCs, PyLoader and PyPycLoader, which help with implementing source and source/bytecode loaders by implementing load_module in terms of other methods. This removes a lot of gritty details loaders typically have to worry about.
2009-03-09 03:35:50 +00:00
* Implement InspectLoader for BuiltinImporter and FrozenImporter.
Add importlib.machinery with its first tenants, BuitinImporter and FrozenImporter. Docs forthcoming. I plan on all finders and loaders (and most likely hooks) to live in imoprtlib.machinery. Utility stuff will end up in importlib.util. Higher-level API stuff will stay on imoprtlib directly (e.g. import_module).
2009-01-22 22:43:07 +00:00
Introduce importlib.abc. The module contains various ABCs related to imports (mostly stuff specified by PEP 302). There are two ABCs, PyLoader and PyPycLoader, which help with implementing source and source/bytecode loaders by implementing load_module in terms of other methods. This removes a lot of gritty details loaders typically have to worry about.
2009-03-09 03:35:50 +00:00
+ Expose function to see if a frozen module is a package.
Rewrite the code implementing __import__ for importlib. Now it is much simpler and relies much more on meta path finders to abstract out various parts of import. As part of this the semantics for import_module tightened up and now follow __import__ much more closely (biggest thing is that the 'package' argument must now already be imported, else a SystemError is raised).
2009-02-07 01:15:27 +00:00
Add some notes about importlib and some API exposure cleanup.
2009-02-21 03:12:17 +00:00
* Remove ``import *`` from importlib.__init__.
* Remove __all__ from importlib._bootstrap.
* Add leading underscores to all objects in importlib._bootstrap that are not
publicly exposed.
Refactor source and bytecode file loaders in importlib so that there are source-only and source/bytecode loaders.
2009-02-21 05:41:15 +00:00
* Reorder importlib/_bootstrap.py so definitions are not in inverted order.
Document importlib.machinery.PathFinder.
2009-02-16 04:18:01 +00:00
* Make sure that there is documentation *somewhere* fully explaining the
semantics of import that can be referenced from the package's documentation
(even if it is in the package documentation itself, although it might be best
in the language specification).