methods change slightly, and explicit field definitions (using |
methods change slightly, and explicit field definitions (using |
'model.structField' or similar) are required. See PEAK's 'URL.Base' |
'model.structField' or similar) are required. See PEAK's 'URL.Base' |
subclasses for examples. There is also a sophisticated parsing and |
subclasses for examples. There is also a sophisticated parsing and |
formatting framework that can be used in place of the old regex-based |
formatting framework (see the 'peak.naming.URL' and 'peak.util.fmtparse' |
approach. |
modules) that can be used in place of the old regex-based approach. |
|
|
|
- Added 'peak.util.fmtparse', a parsing and formatting framework, and |
|
integrated it with 'peak.model' so that any element type can have a |
|
syntax for parsing from, or formatting to, a string. |
|
|
- Added 'binding.whenAssembled(...)' as syntax sugar for |
- Added 'binding.whenAssembled(...)' as syntax sugar for |
'binding.Once(...,activateUponAssembly=True)'. |
'binding.Once(...,activateUponAssembly=True)'. |