++++++++++
Pysistency
++++++++++
Python containers with persistency
|landscape| |travis| |codecov|
`pysistency` provides clones of standard containers backed by persistent data
storage. These containers allow to wrk with data too large for memory, and to
seamlessly keep data across program executions.
.. |landscape| image:: https://landscape.io/github/maxfischer2781/pysistency/master/landscape.svg?style=flat
:target: https://landscape.io/github/maxfischer2781/pysistency/develop
:alt: Code Health
.. |travis| image:: https://travis-ci.org/maxfischer2781/pysistency.svg?branch=develop
:target: https://travis-ci.org/maxfischer2781/pysistency
:alt: Test Health
.. |codecov| image:: https://codecov.io/gh/maxfischer2781/pysistency/branch/develop/graph/badge.svg
:target: https://codecov.io/gh/maxfischer2781/pysistency
:alt: Code Coverage
.. contents:: **Table of Contents**
:depth: 2
Containers
==========
Efficiently implementing each container requires code tailored to its data
structure and usage. Each implementation is developed separately from others.
================ =========================================== ==============
Python Pysistency Status
================ =========================================== ==============
`dict` `pysistency.pdict.PersistentDict` Stable
`list` `pysistency.plist.PersistentList` Experimental
================ =========================================== ==============
The following `Status` categories are used:
**Experimental**
Public interfaces and data storage may change at any time. Functionality
is lacking.
**Stable**
Core functionality fully implemented, data storage will remain stable.
Some functionality still missing.
**Complete**
All functionality available. Internal implementation details may change.
**Done**
All functionality available, internal implementation stable, passes all
applicable, official tests.
Where's X?
==========
Priority for new/existing types depends mostly on ease of implementation and
need. If you require a specific type or interface, let me know.
Backends
========
The containers of `pysistency` rely on backends to store data. This allows
switching the storage backend for each container. Currently, there is only
one backend: a file-based backend using `pickle`.
Pysistency
++++++++++
Python containers with persistency
|landscape| |travis| |codecov|
`pysistency` provides clones of standard containers backed by persistent data
storage. These containers allow to wrk with data too large for memory, and to
seamlessly keep data across program executions.
.. |landscape| image:: https://landscape.io/github/maxfischer2781/pysistency/master/landscape.svg?style=flat
:target: https://landscape.io/github/maxfischer2781/pysistency/develop
:alt: Code Health
.. |travis| image:: https://travis-ci.org/maxfischer2781/pysistency.svg?branch=develop
:target: https://travis-ci.org/maxfischer2781/pysistency
:alt: Test Health
.. |codecov| image:: https://codecov.io/gh/maxfischer2781/pysistency/branch/develop/graph/badge.svg
:target: https://codecov.io/gh/maxfischer2781/pysistency
:alt: Code Coverage
.. contents:: **Table of Contents**
:depth: 2
Containers
==========
Efficiently implementing each container requires code tailored to its data
structure and usage. Each implementation is developed separately from others.
================ =========================================== ==============
Python Pysistency Status
================ =========================================== ==============
`dict` `pysistency.pdict.PersistentDict` Stable
`list` `pysistency.plist.PersistentList` Experimental
================ =========================================== ==============
The following `Status` categories are used:
**Experimental**
Public interfaces and data storage may change at any time. Functionality
is lacking.
**Stable**
Core functionality fully implemented, data storage will remain stable.
Some functionality still missing.
**Complete**
All functionality available. Internal implementation details may change.
**Done**
All functionality available, internal implementation stable, passes all
applicable, official tests.
Where's X?
==========
Priority for new/existing types depends mostly on ease of implementation and
need. If you require a specific type or interface, let me know.
Backends
========
The containers of `pysistency` rely on backends to store data. This allows
switching the storage backend for each container. Currently, there is only
one backend: a file-based backend using `pickle`.
Metadata
Release files for pysistency 0.1.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 | |
|---|---|---|---|
| pysistency-0.1.0.tar.gz | 16.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pysistency-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.8 kB
Release files / pysistency-0.1.0.tar.gz
| Download URL | pysistency-0.1.0.tar.gz |
|---|---|
| Size | 16.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f539d4ca3f25ae96eed5133fe0aa29e3bf9c3013d107154a2e36a85cd66d7ee0
|
|
BLAKE2b-256 checksum How to use checksums |
70044d7ae4ca1ac25e66e5a31136cf13312cad1de4a13d02b47d328552797edd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / pysistency-0.1.0-py3-none-any.whl
| Download URL | pysistency-0.1.0-py3-none-any.whl |
|---|---|
| Size | 20.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
583e30bc55d01757da78e4de3e1e968878917762c288f31f2d73c6c793dab0a8
|
|
BLAKE2b-256 checksum How to use checksums |
e360d839bd55127bea711baa698ec0a6cd8688b39a8552d81e8ece3df7701516
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |