diff options
| author | Chris McDonough <chrism@plope.com> | 2009-04-23 01:24:17 +0000 |
|---|---|---|
| committer | Chris McDonough <chrism@plope.com> | 2009-04-23 01:24:17 +0000 |
| commit | 23dcde9a953a577d480116c6e0323e4fd3980d96 (patch) | |
| tree | 555e1fff3db2d729195f1140c4d15c4b5ff6f77f /src | |
| parent | f7272e2562d236d8b718eda82586765497ff020f (diff) | |
| download | zope-interface-23dcde9a953a577d480116c6e0323e4fd3980d96.tar.gz | |
Confusion.
Diffstat (limited to 'src')
| -rw-r--r-- | src/zope/interface/adapter.py | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/src/zope/interface/adapter.py b/src/zope/interface/adapter.py index a8dd335..095400f 100644 --- a/src/zope/interface/adapter.py +++ b/src/zope/interface/adapter.py @@ -39,6 +39,13 @@ class BaseAdapterRegistry(object): # {provided -> {name -> valie}} # but for order == 2, we have: # {r1 -> {r2 -> {provided -> {name -> valie}}}} + # + # XXX ^^^ what does the above comment have to do with any code + # in this method? and.. "interfaces is really a nested key"? + # i don't see "interfaces" mentioned. does it mean + # "provided"? what are r1 and r2? why is the structure just + # below this a list? is this comment 100% bitrotten or just a + # little? /XXX self._adapters = [] # {order -> {required -> {provided -> {name -> [value]}}}} @@ -64,6 +71,8 @@ class BaseAdapterRegistry(object): # so have to check the generations of base registries to determine # if their cache data are current + # ^^^ XXX what are the above comments describing? /XXX + # Base registries: self.__bases__ = bases |