This project has been archived by its maintainers, and is no longer receiving any updates.
This package provides several extensions to Zope interfaces, such as a persistent implementation, interface type queries, and a vocabulary of all registered interfaces of the system (or of a particular type).
CHANGES
3.6.0 (2010-09-20)
Added test extra to declare test dependency on zope.testing.
Moved zope.app.interfaces.queryType to zope.app.content to inverse dependency, leaving BBB import here.
3.5.2 (2010-07-08)
3.5.1 was a bad release
3.5.1 (2010-07-07)
Fixed tests and test tearDown to actually close the DB.
3.5.0 (2009-05-21)
Factor out ObjectInterfacesVocabulary into zope.componentvocabulary.
Remove various test dependencies.
3.4.0 (2007-10-24)
Initial release independent of the main Zope tree.
Metadata
Release files for zope.app.interface 3.6.0
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 | |
|---|---|---|---|---|
| zope.app.interface-3.6.0.tar.gz | 6.0 kB | Without provenance | Details |
Release files / zope.app.interface-3.6.0.tar.gz
| Download URL | zope.app.interface-3.6.0.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3a8bbbce068c5b1df7afcf31abd212eb58b3a58e5ab3ab5407c164168223e464
|
|
BLAKE2b-256 checksum How to use checksums |
2635207d0d0fd1033ed25ed291480f5e4b2bf44f15b670b93836559cca5e9432
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for zope.app.interface 3.6.0
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.
