This repository has been archived by the owner on Dec 21, 2020. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Removal of Services. You can now access the adapter and utiliy
registry directly via the site manager's `adapters` and `utilities` attribute, respecitvely. + Converted Principal Annotation Service to be a utility. Added database evolution code to convert all service instances to utilities. + Converted FSSync Service to be a utility. + Created the concept of a global site manager. The adapter and utility registry, formerly the adapter and utility service, are now managed by the site manager. + The `zope.app.utility` package has been merged into `zope.app.component`. The utility registration class is in `site.py`. The utility vocabulary is in `vocabulary.py`. + The `zope.app.site` package has been merged into `zope.app.component`. The site code can be found in `site.py`. + Fixed persistent modules code. Persistent modules are now simply utilities providing `IModuleManager`. The local site manager also does not know any thing about persistent modules anymore. + Updated `zope.app.pluggableauth`, so that it will work as an authentication utility. + Restructured `zope.app.persentation` (a.k.a page folders) to the new component API. - Simplified the registration framework by only supporting two states: active and inactive. This allowed us to get rid of the registration stack and the complexity it introduced to the site management. - Removed all presentation-related APIs from `zope.component`. This included the removal of presentation-related interfaces and the deprecation of all view-related API functions. One should use the adapter API functions instead. - Implemented some initial deprecation framework, see `zope.deprecation`. It allows one to deprecate methods and properties in classes as well as any name in a module. - Moved reusable test setups/APIs from `zope.app.tests` to `zope.app.testing`. No reusable testing code should be in a `tests` package or module.
- Loading branch information