Overview
A storage implementation which uses RAM to persist objects, much like MappingStorage. Unlike MappingStorage, it needs not be packed to get rid of non-cyclic garbage and it does rudimentary conflict resolution. This is a ripoff of Jim’s Packless bsddb3 storage.
Changelog
5.2 (2021-07-05)
Update package configuration
Package is now officially undeprecated because the data corruption issue - that was the reason for its deprecation - has been understood and fixed. See (#16).
Add support for Python 3.8 and Python 3.9.
5.1 (2019-08-15)
5.0 (2019-05-10)
Update PyPy version.
Drop Python 3.4 support.
Add support for Python 3.7.
Avoid RuntimeError in _takeOutGarbage. See issue 7.
4.0.1 (2017-11-27)
Raise POSKeyError instead of KeyError in loadBefore.
4.0 - 2017-03-09
Drop Python 3.3 compatibility, add Python 3.6 compatibility.
Require ZODB 5.0 or newer.
Use storage._lock as a context manager.
Declare PyPy compatibility.
3.0 - 2016-04-03
Python 3.3-3.5 compatibility.
2.12.2 - 2012-10-14
Explicitly state distribution dependencies instead of re-using the ZODB test requirements.
2.12.1 - 2010-09-29
Disabled check_tid_ordering_w_commit test from BasicStorage, as it uses invalid test data.
2.12.0 - 2010-09-25
Require at least ZODB 3.9 and adjusted method signatures to disuse versions.
Expanded dependency on ZODB3 to include the test extra.
2.11.3 - 2010-06-05
Approximate PEP8 compliance.
Split out the ZODB protocol tests from the tests specific to the module. Make the local tests use “normal” unittest conventions.
Comply with repository policy.
Clean imports, docstrings; add an instance-level hook for GC parms.
Fix a test failure due to never-unghostified root in second connection.
2.11.2 - 2009-08-03
Added change log and readme.
Lauchpad #143736, #271395: fixed AttributeError’ on _ltid in TempStorage
2.11.1 - 2008-08-05
Initial release as a stand-alone package.
Release files for tempstorage 5.2
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 |
|---|---|---|---|---|
| tempstorage-5.2.tar.gz | 13.1 kB | Without provenance | Details for tempstorage-5.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tempstorage-5.2-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for tempstorage-5.2-py2.py3-none-any.whl |
Total release size: 26.4 kB
Release files / tempstorage-5.2.tar.gz
| Download URL | tempstorage-5.2.tar.gz |
|---|---|
| Size | 13.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6a82f266fcaa103117039c903d8956dce33f08edd66ded3bd10550e98f7e17d2
|
|
BLAKE2b-256 checksum How to use checksums |
442d8f0a353a697126fe540bf6c5483e62ca515f8dbe4c93093e35c7d32566f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.1 CPython/3.7.5
|
Release files / tempstorage-5.2-py2.py3-none-any.whl
| Download URL | tempstorage-5.2-py2.py3-none-any.whl |
|---|---|
| Size | 13.2 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
d5c242f3e85f0b212918f03d035875c055576593ac8351e343a4f6f7de37631e
|
|
BLAKE2b-256 checksum How to use checksums |
066c9349f848b3afe29764f1ab54f03725422bd3d9c2869d8a85a8a356ec35a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.1 CPython/3.7.5
|
Security for tempstorage 5.2
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.
