| |
Fixes and Enhancements since Version 0.5 alpha 2 |
| |
|
| |
Changed, Enhanced, or Newly Deprecated Features |
| |
|
| |
- 'peak.naming' no longer automatically converts all addresses to the |
| |
addressed objects. You must specifically request the interface you want |
| |
by adapting the retrieved object to that interface. This can be done by |
| |
supplying an 'adaptTo=ISomething' keyword argument to the attribute binding |
| |
definition or your 'lookupComponent()' call. |
| |
|
| |
The naming system no longer has 'objectFactories' and 'stateFactories'; |
| |
these have been replaced with adaptation. Writable naming contexts must |
| |
have a 'serializationProtocol' attribute specifying what interface an object |
| |
should be adapted to before attempting to store it in that context. |
| |
|
| |
The naming system no longer processes the 'creationName' keyword argument; |
| |
this is now considered the sole responsibility of 'peak.binding'. The |
| |
'IComponent.lookupComponent()' method still accepts the keyword argument, |
| |
and attribute bindings still handle the creation name transparently. It is |
| |
just not available via naming system APIs, and naming contexts no longer |
| |
have to deal with it. |
| |
|
| |
The naming system base classes no longer use 'attrs' as an input parameter |
| |
or return value. If you've subclassed anything from 'peak.naming.contexts', |
| |
note that your '_get()' methods should now just return the lookup value, |
| |
rather than a 'state,attrs' tuple. For most naming contexts, this just |
| |
means you should change 'return foo, None' statements to just 'return foo'. |
| |
|
| |
- REMOVED 'naming.ParsedURL'; it was deprecated as of 0.5 alpha 2. |
| |
|
| |
- The 'provides' keyword argument to various 'peak.binding' APIs has been |
| |
renamed to 'offerAs', and it must be a sequence of configuration keys. |
| |
(Previously, it accepted either a single key or a tuple of keys.) |
| |
The signature of 'binding.Constant()' was changed as well; the first |
| |
positional argument is now the constant value, and 'offerAs' is now a |
| |
keyword argument. (Previously, 'provides' was the first positional argument |
| |
of 'binding.Constant()'.) The 'registerProvider()' method of |
| |
'config.IConfigurable()' also now accepts only a single configuration key, |
| |
as does 'EigenRegistry.register()'. |
| |
|
| |
Also, all 'peak.binding' APIs now only accept positional parameters for |
| |
items unique to that API. Items common to multiple APIs (such as 'offerAs', |
| |
'doc', 'attrName', etc.) should now be supplied as keyword arguments. |
| |
|
| |
Bindings also now automatically "suggest" the containing object as a parent |
| |
component for the contained object, whenever a value is assigned to them or |
| |
computed. If a non-None 'adaptTo' is set on the binding, the value assigned |
| |
or computed will be adapted to the specified protocol before the parent |
| |
component is suggested. 'binding.New()' no longer relies on the |
| |
'IComponentFactory' interface, but instead uses the new adapt/suggest |
| |
mechanisms. |
| |
|
| |
Previously, parent components were only "suggested" when a binding was set |
| |
via component constructor keyword arguments. Now, this is done at any time |
| |
bindings are set, but *not* for non-binding keyword arguments. In other |
| |
words, ordinary attributes of a component do not receive "suggested parent" |
| |
notices, even when set via constructor keyword arguments. If you want an |
| |
attribute to do this, you must define the attribute with the binding API; |
| |
e.g. via 'requireBinding()' or 'binding.Constant()'. |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| Fixes and Enhancements since Version 0.5 alpha 1 |
Fixes and Enhancements since Version 0.5 alpha 1 |
| |
|
| Changed, Enhanced, or Newly Deprecated Features |
Changed, Enhanced, or Newly Deprecated Features |
| |
|
| |
- Added a 'shellcmd:' URL scheme that returns a function that calls |
| |
'os.system()' on the body of the URL. It's intended for use as a command |
| |
factory, as is needed by the 'URLChecker' periodic task. |
| |
|
| |
- You can now define adapters from arbitrary types to 'binding.IBindingNode', |
| |
and thus be able to use them as part of a component hierarchy - without |
| |
needing to directly add 'getParentComponent()' or 'getComponentName()' |
| |
methods to them. |
| |
|
| |
- Added experimental 'invoke.c' script for POSIX-ish platforms with funky |
| |
'#!' support, or lack thereof. |
| |
|
| |
'invoke' is designed to be used like this:: |
| |
|
| |
#!/usr/local/bin/invoke peak somearg otherarg... |
| |
|
| |
This should work on most sane platforms with a long-enough commandline. |
| |
(See "this page":http://homepages.cwi.nl/~aeb/std/hashexclam-1.html for |
| |
details on the insanely incompatible ways different Unixes interpret '#!' |
| |
lines.) |
| |
|
| |
The script is not currently built or installed by setup.py. On the |
| |
platforms it's targeted at, you should be able to build it with:: |
| |
|
| |
gcc -o invoke invoke.c |
| |
|
| |
(Yes, it really is that simple of a script.) |
| |
|
| |
- Added a ZConfig schema for 'running.commands.EventDriven' applications, |
| |
a ZConfig component definition for adaptive tasks, and a running shortcut |
| |
called 'EventDriven'. |
| |
|
| |
It should now be possible to do this:: |
| |
|
| |
#!/usr/bin/env peak EventDriven |
| |
|
| |
at the top of a ZConfig file formatted according to the new schema, and |
| |
have it run. There are two periodic tasks that can be configured and |
| |
run from such a file: 'CleanupFiles' and 'URLChecker'. 'CleanupFiles' will |
| |
delete files matching a pattern that are older than a certain age, while |
| |
'URLChecker' will check to see if the target of a naming system URL is |
| |
up/available/working, and if not, runs a command to restart it. As an |
| |
amusing demo, try specifying a 'file:' URL with a 'shellcmd:touch theFile' |
| |
to recreate the file, then add a 'CleanupFiles' that deletes the file the |
| |
checker looks for. This can be hours (well, minutes) of exciting fun as you |
| |
watch the dueling daemons undoing each others' work. |
| |
|
| - Added 'zconfig.schema' URL scheme that loads an enhanced ZConfig schema |
- Added 'zconfig.schema' URL scheme that loads an enhanced ZConfig schema |
| object that can act as a command line interpreter using the 'peak' script. |
object that can act as a command line interpreter using the 'peak' script. |
| |
|
| To use it, run 'peak zconfig.schema:urlToSchema urlOfConfig'. Or, add |
To use it, run 'peak zconfig.schema:urlToSchema urlOfConfig'. Or, add |
| a line like this:: |
a line like this:: |
| |
|
| |
|
| - Added support in the mof2py code generator for "unprefixing" enumerated |
- Added support in the mof2py code generator for "unprefixing" enumerated |
| values, so that UML and other metamodels' enumerations work correctly |
values, so that UML and other metamodels' enumerations work correctly |
| when loading from XMI. |
when loading from XMI. Also, mof2py no longer emits 'config.setupModule()' |
| |
calls in generated code, as in practice they are not needed. |
| |
|
| |
- Running 'peak test' from the command line is roughly equivalent to running |
| |
'unittest.py', except that the test suite defaults to the PEAK test suite. |
| |
You can, however run any test suite from the command line with a dotted |
| |
module/attribute path, e.g 'peak test foo.bar.test_suite'. |
| |
|
| - 'binding.Acquire()' now accepts a 'default' value argument, and |
- 'binding.Acquire()' now accepts a 'default' value argument, and |
| 'binding.New()' no longer accepts the 'bindToOwner' flag. |
'binding.New()' no longer accepts the 'bindToOwner' flag. |
| about this, as they are part of the naming package's extensibility |
about this, as they are part of the naming package's extensibility |
| framework.) |
framework.) |
| |
|
| - 'EigenRegistry' and 'PropertyMap' no longer attempt to figure out whether |
|
| implied (i.e. inherited) interfaces are more or less general with respect |
|
| to a previous registration. This was behavior that emulated Zope adapter |
|
| registries, but what we really wanted was more akin to a Zope "type" |
|
| registry. The only parts of the test suite that used the old behavior |
|
| were the tests specifically written to ensure that behavior! |
|
| |
|
| - 'binding.bindTo()' now accepts a 'default=' argument, whose value will be |
- 'binding.bindTo()' now accepts a 'default=' argument, whose value will be |
| used in case of a 'NameNotFound' error. |
used in case of a 'NameNotFound' error. |
| |
|
| |
|
| Corrected Problems |
Corrected Problems |
| |
|
| |
- Fixed a problem in ZConfig 'schema.dtd'; I used 'PCDATA' where I should've |
| |
used 'CDATA'. |
| |
|
| |
- Fixed a problem with 'binding.supertype()' not working correctly if the MRO |
| |
it was searching contained a "classic" class. Now 'supertype()' skips any |
| |
classic classes it finds. (It probably should be rewritten entirely.) |
| |
|
| |
- Fixed misc. problems with 'fromZConfig()' component constructor |
| |
|
| - Fixed source distributions missing essential setup files |
- Fixed source distributions missing essential setup files |
| |
|
| - Fixed a problem with assembly events, where a parent component that didn't |
- Fixed a problem with assembly events, where a parent component that didn't |
| if they requested the notification after the parent had already received |
if they requested the notification after the parent had already received |
| it. |
it. |
| |
|
| |
- Fixed a bug in automatic metaclass generation that caused extra unneeded |
| |
metaclasses to be generated. |
| |
|
| - Fixed 'naming.lookup()' and related APIs not setting the parent component |
- Fixed 'naming.lookup()' and related APIs not setting the parent component |
| of created objects without an explicitly supplied 'creationParent' keyword |
of created objects without an explicitly supplied 'creationParent' keyword |
| argument. This used to "sort of work" when we had implicit configuration |
argument. This used to "sort of work" when we had implicit configuration |
Diff of /PEAK/CHANGES.txt
Parent Directory
| 
Revision Log