zope.rdb
Overview
Zope RDBMS Transaction Integration.
Provides a proxy for interaction between the zope transaction framework and the db-api connection. Databases which want to support sub transactions need to implement their own proxy.
Change History
3.5.0 (2009/01/31)
Use zope.container instead of zope.app.container.
3.4.2 (2008/10/10)
Re-release 3.4.1
3.4.1 (2008/10/10)
Remove body of DatabaseException, base Exception class already provides the same functionality.
Use hashlib.md5 instead of md5.new if available. md5 module is deprecated and will be removed in a future Python release.
Remove usage of ‘as’ as variable name. ‘as’ is a keyword in Python 2.6 and generates a SyntaxError.
3.4.0 (2007/09/01)
Initial release as an independent package
Download
Metadata
Release files for zope.rdb 3.5.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 | Actions |
|---|---|---|---|---|
| zope.rdb-3.5.0.tar.gz | 198.9 kB | Without provenance | Details for zope.rdb-3.5.0.tar.gz |
Release files / zope.rdb-3.5.0.tar.gz
| Download URL | zope.rdb-3.5.0.tar.gz |
|---|---|
| Size | 198.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
588c98db41960013740d9c204d8a78f87ac557d9605d898b93ba13e3bc308bf1
|
|
BLAKE2b-256 checksum How to use checksums |
be9a10ca538ea0a0a47d3c2872635ab8d4e180aea41825049bd306587618147f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for zope.rdb 3.5.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.
