Skip to main content

Cleanup of keys leftover in zope component registries

Project description

cleanup_zope_persistent_registry

Before 3.5.2, zope.interface was broken : it did not remove keys when unregistering adapters or unsubscribing subscribers.

This implies that even when proper unregistration of adapters and subscribers had been done, interfaces were left over, pickled in persistent registries.

This leads to nasty bugs when the code that defined those interfaces is removed from the system.

This package defines a function that cleans up those leftover interfaces. It must be called on a site manager, instance of PersistentComponents like the local site manager of a Plone site:

from zope.component import getSiteManager
from cleanup_zope_persistent_registry import cleanup_leftovers

site_manager = getSiteManager(my_plone_site)
cleanup_leftovers(site_manager)

Tested

https://secure.travis-ci.org/gotcha/cleanup_zope_persistent_registry.png?branch=master

Changelog

0.1.1 (2012-10-03)

  • Fix : cleanup was not properly persisted.

0.1 (2012-08-20)

  • Initial release.

Project details


Download files

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

Source Distribution

cleanup_zope_persistent_registry-0.1.1.zip (7.9 kB view details)

Uploaded Source

File details

Details for the file cleanup_zope_persistent_registry-0.1.1.zip.

File metadata

File hashes

Hashes for cleanup_zope_persistent_registry-0.1.1.zip
Algorithm Hash digest
SHA256 c7186fd40ff9d4eedb0173c6f8b48c8b3d57371ef438856e834b77bc73a3a60b
MD5 8dacdeef5514576c397be4043fcd6757
BLAKE2b-256 696c13a4448876e8c7970d3e333b111b43daa5d6ed53553584ee66ebfdbbfaa9

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page