E&S CVS Commit: PEAK - Reversed parameter order for both findUtility and getProperty. Now the

pje at eby-sarna.com pje at eby-sarna.com
Sun Oct 13 17:37:00 EDT 2002

Module Name:	PEAK
Committed By:	pje
Date:		Sun Oct 13 21:36:03 UTC 2002

Modified Files:
	PEAK/src/peak/binding: components.py
	PEAK/src/peak/binding/tests: __init__.py
	PEAK/src/peak/config: api_impl.py
	PEAK/src/peak/config/tests: __init__.py
	PEAK/src/peak/naming: contexts.py names.py spi.py
	PEAK/src/peak/storage: transactions.py

Log Message:
Reversed parameter order for both findUtility and getProperty.  Now the
name or interface comes first, and the (now optional) target component
second.  This means that when writing short scripts or using PEAK at an
interpreter prompt, it won't be necessary to pass config.getLocal() into
either function just to get access to a global utility or property.

I'd like to make lookupComponent and certain other functions follow this
same pattern, but there are some hitches to doing so right away.  I'll
take another stab at it later.

Also, I added '!' and ':' to the allowable characters in a property name,
since cygwin Python puts things like '!C:' into os.environ.keys().  Last,
but not least, I added an 'onJoinTxn()' method to TransactionComponent, as
I'm about to need it in order to implement transaction operations on
ManagedConnection objects.

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

To generate a diff of this commit:
cvs rdiff -r1.47 -r1.48 PEAK/src/peak/binding/components.py
cvs rdiff -r1.16 -r1.17 PEAK/src/peak/binding/tests/__init__.py
cvs rdiff -r1.6 -r1.7 PEAK/src/peak/config/api_impl.py
cvs rdiff -r1.3 -r1.4 PEAK/src/peak/config/tests/__init__.py
cvs rdiff -r1.19 -r1.20 PEAK/src/peak/naming/contexts.py
cvs rdiff -r1.18 -r1.19 PEAK/src/peak/naming/names.py
cvs rdiff -r1.24 -r1.25 PEAK/src/peak/naming/spi.py
cvs rdiff -r1.11 -r1.12 PEAK/src/peak/storage/transactions.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