Introduction
collective.forgetit removes residue of Products that have been removed. It will not delete your content objects. Use the ZMI for that. It will not remove persistent utilities. Use wildcard.fixpersistentutilities for that. collective.forgetit aims to remove traces in the other locations, one of them being the catalog from zc.relation, where a removed interface can create havoc.
While collective.forgetit does not remove your content objects, it removes other information that might have been of value. Be sure that you really don’t want to reinstall the package/Product again to reuse your old content!
Currently, collective.forgetit only handles residue in zc.relation catalogs.
Contributors
Patrick Gerken, Original authore
Changelog
0.0.1 (2012-09-21)
Initial release [do3cc]
1 maintainer
Metadata
1 maintainer
Release files for collective.forgetit 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| collective.forgetit-0.0.1.zip | 9.4 kB | Without provenance | Details for collective.forgetit-0.0.1.zip |
Release files / collective.forgetit-0.0.1.zip
| Download URL | collective.forgetit-0.0.1.zip |
|---|---|
| Size | 9.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8c717bcd572b858b372d5fd078e3cddb0a09008a081a5e6c22e4c522d8860f84
|
|
BLAKE2b-256 checksum How to use checksums |
2d3c320cfecd1f6fb7fe5fe7bb72ce4bcb137b11c8d0de1deea7140c96413b37
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.forgetit 0.0.1
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.
