Stowage/cpython
2
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-10-31 13:41:24 +00:00
Code Issues Projects Releases Packages Wiki Activity
cpython/Lib/importlib/NOTES

111 lines
2.3 KiB
Text
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
/////
Add a NOTE that alternative VMs should be supported by importlib in a nicer fashion by factoring out bytecode support.
2009-02-09 21:51:29 +00:00
* Refactor source/bytecode finder/loader code such that bytecode support is a
subclass of source support (makes it nicer for VMs that don't use CPython
bytecode).
Separate out finder for source and source/bytecode.
2009-02-21 03:31:35 +00:00
+ PyLoader (for ABC)
Outline a possible way to separate out source loading from bytecode loading.
2009-02-17 07:15:17 +00:00
Tweak the source/bytecode loader from importlib to use more of the PEP 302 protocol API.
2009-02-21 03:53:06 +00:00
- load_module for source only
Outline a possible way to separate out source loading from bytecode loading.
2009-02-17 07:15:17 +00:00
- get_code for source only
Separate out finder for source and source/bytecode.
2009-02-21 03:31:35 +00:00
+ PyFileLoader(PyLoader)
Outline a possible way to separate out source loading from bytecode loading.
2009-02-17 07:15:17 +00:00
- get_data
- source_mtime
- source_path
Separate out finder for source and source/bytecode.
2009-02-21 03:31:35 +00:00
+PyPycLoader (PyLoader, for ABC)
Tweak the source/bytecode loader from importlib to use more of the PEP 302 protocol API.
2009-02-21 03:53:06 +00:00
- load_module for source and bytecode
Separate out finder for source and source/bytecode.
2009-02-21 03:31:35 +00:00
- get_code for source and bytecode
+ PyPycFileLoader(PyPycLoader, PyFileLoader)
Outline a possible way to separate out source loading from bytecode loading.
2009-02-17 07:15:17 +00:00
- bytecode_path
- write_bytecode
Update NOTES for importlib.
2009-01-26 01:54:40 +00:00
* Implement PEP 302 protocol for loaders (should just be a matter of testing).
+ Source/bytecode.
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
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
+ abc
- Finder
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
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
* find_module
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
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
- Loader
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
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
* load_module
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
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
- (?) Importer(Finder, Loader)
- ResourceLoader(Loader)
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
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
* get_data
Finish implementing tests for importlib.machinery.PathFinder by testing that implicit hooks are handled properly.
2009-02-06 00:07:49 +00:00
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
- InspectLoader(Loader)
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
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
* is_package
* get_code
* get_source
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
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
- (?) SourceLoader(ResourceLoader)
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
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
* source_path
* bytecode_path
* write_bytecode (not abstract)
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
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
+ util
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
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
- set___package__ decorator
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
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
+ machinery
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
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
- Extensions importers
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
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
* ExtensionFinder
* (?) Loader
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
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
- Source/bytecode importers
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
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
* SourceFinder
* (?) Loader
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
Minor NOTES changes for importlib.
2009-02-21 02:51:12 +00:00
+ test (Really want to worry about compatibility with future versions?)
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
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
- abc
NOTES for importlib should mention the ultimate end-goal for the package.
2009-01-18 00:36:55 +00:00
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
* FinderTests [doc]
* LoaderTests [doc]
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.
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).
Update importlib notes.
2009-02-01 05:55:23 +00:00
* Write benchmark suite.
* OPTIMIZE!
Finish implementing tests for importlib.machinery.PathFinder by testing that implicit hooks are handled properly.
2009-02-06 00:07:49 +00:00
+ Fast path absolute name.
+ Fast path pulling from sys.modules.
Update importlib notes.
2009-02-01 05:55:23 +00:00
NOTES for importlib should mention the ultimate end-goal for the package.
2009-01-18 00:36:55 +00:00
* Bootstrap importlib as implementation of builtins.__import__
Add some notes for importlib to package up what is in Python 2.7 as well as modules that can probably get replaced by importlib at some point.
2009-02-02 20:32:29 +00:00
* Replace standard library modules.
+ imp
+ py_compile
+ compileall
Reference in a new issue Copy permalink