Skip to main content
Help the Python Software Foundation raise $60,000 USD by December 31st!  Building the PSF Q4 Fundraiser

Local site manager implementation for Zope 2

Project description

Introduction

Overview

five.localsitemanager attempts to provide a local site manager implementation that is as close to Zope 3’s implementation as possible. Some reservations that do not conflict with Zope 3 have been made to ease the path with CMF.

Developer Resources

Installation

Prerequisites

Installation

Place the five top-level package into your instance’s lib/python directory. You can also install it as an egg using easy_install, for example into your instance by turning it into a workingenv.

Configuration

Place a five.localsitemanager-configure.zcml file into your instance’s etc/package-includes directory with the following contents:

<include package="five.localsitemanager" />

Also setup a five.localsitemanager-overrides.zcml file into your instance’s etc/package-includes directory with the following contents:

<include package="five.localsitemanager" file="overrides.zcml" />

Running the Tests

Use the following command to run this package’s tests:

$ bin/zopectl test -s five.localsitemanager

Changelog

1.0c1 - 2008-08-27

  • Added buildout for project, so testing can be done using bin/test. [icemac]

  • Added ability to register utilities with an absolute path. These utilities are returned wrapped into their original context. This change is backward compatible to existing registries.

    But registering utilities having an acquisition context will behave different because these utilities will be returned in their original context. To restore the previous behavior, register utilities unwrapped (aq_base).

    For storing path information the component must implement getPhysicalPath and have an absolute path.

    When a component registered as utility is moved and registered again the path stored in registry gets updated. [icemac]

0.4 - 2008-07-23

  • Rewrite PersistentComponents.registeredUtilities to not use internal methods. This makes it compatible with both zope.component <3.5.0dev and >3.5.0dev. [wichert]

0.3 - 2007-12-24

  • Fixed potential aq problem when assigning various values to the utilities registry of the component registry. [hannosch]

0.2 - 2007-06-30

  • Refactored and fixed aq wrapping: Nested site managers now return utilities wrapped in the right context. RequestContainers are removed and wrapped utilities are cached. This requires a special LookupClass called ‘FiveVerifyingAdapterLookup’ in all ‘utilities’ registries used below a five.localsitemanager site. [yuppie, hannosch]

0.1.2 - 2007-06-23

  • Corrected the zip-safe flag to be False.

0.1.1 - 2007-03-05

  • Fixed aq wrapping when looking up a utility that is actually the component registry’s parent (the ISite).

0.1 (2007-02-27)

  • Initial version

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Files for five.localsitemanager, version 1.0c1
Filename, size File type Python version Upload date Hashes
Filename, size five.localsitemanager-1.0c1.tar.gz (14.7 kB) File type Source Python version None Upload date Hashes View

Supported by

Pingdom Pingdom Monitoring Google Google Object Storage and Download Analytics Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page