Revision 1282

Jump to revision:
Author:	pje
Date:	Mon Jul 28 22:06:39 2003 UTC (20 years, 9 months ago)

Log Message:

It's now possible to declare an attribute as offering a wildcard property;
such lookups now follow the same rules as other wildcard property lookups.
The 'config.IConfigKey' interface has been changed to cleanly support
implied keys at both registration and lookup time, so you can implement
your own key types that work the way interfaces or property names do for
configuration lookups.

I also moved the 'EigenRegistry' class from 'peak.util.EigenData' to
'peak.config.registries', as it hasn't really been useful outside PEAK for
a while now.

Changed paths:

Path	Action	Text Changes	Prop Changes	Diff to Previous
PEAK/CHANGES.txt	modified	X		(diff to previous)
PEAK/src/peak/api/__init__.py	modified	X		(diff to previous)
PEAK/src/peak/binding/components.py	modified	X		(diff to previous)
PEAK/src/peak/config/config_components.py	modified	X		(diff to previous)
PEAK/src/peak/config/interfaces.py	modified	X		(diff to previous)
PEAK/src/peak/config/registries.py	added	X	X
PEAK/src/peak/config/tests/__init__.py	modified	X		(diff to previous)
PEAK/src/peak/util/EigenData.py	modified	X		(diff to previous)
PEAK/src/peak/util/tests/EigenData.py	modified	X		(diff to previous)