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.

Metadata

Release files for cleanup_zope_persistent_registry 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cleanup_zope_persistent_registry 0.1.1
File	Size	Uploaded	Provenance
cleanup_zope_persistent_registry-0.1.1.zip	7.9 kB	Oct 3, 2012	Without provenance	Details

Release files / cleanup_zope_persistent_registry-0.1.1.zip

Download URL	cleanup_zope_persistent_registry-0.1.1.zip
Size	7.9 kB
Tags	Source
SHA-256 checksum How to use checksums	`c7186fd40ff9d4eedb0173c6f8b48c8b3d57371ef438856e834b77bc73a3a60b`
BLAKE2b-256 checksum How to use checksums	`696c13a4448876e8c7970d3e333b111b43daa5d6ed53553584ee66ebfdbbfaa9`
Upload date	Oct 3, 2012
Uploaded using Trusted Publishing? What is trusted publishing?	No

Security for cleanup_zope_persistent_registry 0.1.1

Report project as malware

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.