For more complex URL classes, the '__init__' methods go away, 'parse' |
For more complex URL classes, the '__init__' methods go away, 'parse' |
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. |
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 |
- Added 'binding.whenAssembled(...)' as syntax sugar for |
'binding.Once(...,activateUponAssembly=True)'. |
'binding.Once(...,activateUponAssembly=True)'. |