| |
|
| Changed, Enhanced, or Newly Deprecated Features |
Changed, Enhanced, or Newly Deprecated Features |
| |
|
| |
- There is now a 'peak.security' package, available from 'peak.api' as |
| |
'security'. It provides permission management functions: you can define |
| |
abstract permissions by subclassing 'security.Permission', then create |
| |
permission checking rules by subclassing 'security.RuleSet', and declare |
| |
the permissions needed to access attributes of a class with |
| |
'security.allow()'. The test suite demonstrates a complex application |
| |
ruleset with dynamic, data-driven permissions. |
| |
|
| |
- There is now an interface for "Active Descriptors": |
| |
'binding.IActiveDescriptor'. 'peak.binding' now uses this interface to |
| |
identify active descriptors, so you can now create your own. (Previously, |
| |
'peak.binding' used 'isinstance()' to detect active descriptors.) |
| |
|
| |
- '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 |
- The 'provides' keyword argument to various 'peak.binding' APIs has been |
| renamed to 'offerAs', and it must be a sequence of configuration keys. |
renamed to 'offerAs', and it must be a sequence of configuration keys. |
| (Previously, it accepted either a single key or a tuple of keys.) |
(Previously, it accepted either a single key or a tuple of keys.) |
| words, ordinary attributes of a component do not receive "suggested parent" |
words, ordinary attributes of a component do not receive "suggested parent" |
| notices, even when set via constructor keyword arguments. If you want an |
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; |
attribute to do this, you must define the attribute with the binding API; |
| e.g. via 'requireBinding()' or 'binding.Constant()'. |
e.g. via 'requireBinding()' or 'binding.Constant()'. If you do *not* want |
| |
a binding to suggest a parent component, use 'suggestParent=False' in the |
| |
binding definition. |
| |
|
| |
|
| |
|
Diff of /PEAK/CHANGES.txt
Parent Directory
| 
Revision Log