Fixes and Enhancements since Version 0.5 alpha 1 |
Fixes and Enhancements since Version 0.5 alpha 1 |
|
|
|
- DEPRECATED 'naming.ParsedURL'. It will disappear in 0.5 alpha 3 or beta. |
|
It is replaced by the new 'naming.URL.Base'. The 'naming.URL' package |
|
provides a new URL parsing framework based on 'peak.model'. Upgrading from |
|
'ParsedURL' to 'URL.Base' is trivial for ParsedURL subclasses that used |
|
only the 'scheme' and 'body' fields, and in fact may not require any |
|
changes except for the choice of base class. |
|
|
|
For more complex URL classes, the '__init__' methods go away, 'parse' |
|
methods change slightly, and explicit field definitions (using |
|
'model.structField' or similar) are required. See PEAK's 'URL.Base' |
|
subclasses for examples. There is also a sophisticated parsing and |
|
formatting framework that can be used in place of the old regex-based |
|
approach. |
|
|
|
- Added 'binding.whenAssembled(...)' as syntax sugar for |
|
'binding.Once(...,activateUponAssembly=True)'. |
|
|
- Removed 'LOG_XYZ' convenience functions from 'peak.api', and refactored |
- Removed 'LOG_XYZ' convenience functions from 'peak.api', and refactored |
'peak.running.logs' to use a PEP 282-like interface, 'running.ILogger'. |
'peak.running.logs' to use a PEP 282-like interface, 'running.ILogger'. |
Under the new scheme, messages must be sent to a specific entry point |
Under the new scheme, messages must be sent to a specific entry point |