E&S CVS Commit: PEAK - Fixed 'naming.lookup()' and related APIs not setting the parent component

pje at eby-sarna.com pje at eby-sarna.com
Sat May 10 10:26:00 EDT 2003

Module Name:	PEAK
Committed By:	pje
Date:		Sat May 10 14:25:16 UTC 2003

Modified Files:
	PEAK/src/peak/naming: api.py contexts.py interfaces.py spi.py

Log Message:
Fixed 'naming.lookup()' and related APIs not setting the parent component
of created objects without an explicitly supplied 'creationParent' keyword
argument.  This used to "sort of work" when we had implicit configuration
parents, but was broken when we went "all explicit" for 0.5 alpha 1.

Also, fixed SPI-level calls that didn't go through "paramegeddon":
'getObjectInstance()', 'getStateToBind()', and 'getURLContext()' weren't
following the "parent/context goes first" signature convention.

To view diffs of this commit, you can use the following URL(s):

To generate a diff of this commit:
cvs rdiff -r1.29 -r1.30 PEAK/CHANGES.txt
cvs rdiff -r1.21 -r1.22 PEAK/src/peak/naming/api.py
cvs rdiff -r1.46 -r1.47 PEAK/src/peak/naming/contexts.py
cvs rdiff -r1.35 -r1.36 PEAK/src/peak/naming/interfaces.py
cvs rdiff -r1.36 -r1.37 PEAK/src/peak/naming/spi.py

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

More information about the source-changes mailing list