Revived
A predictable state container for python heavily inspired by Redux
While not being a strict 1:1 port of Redux API, Revived is supposed to do pretty much the same job in the most pythonic way possible.
NOTE: I needed this piece of code to work with the latest python available at the moment (3.6). While I am not really caring about other versions, the Travis build is running the test suites on all the 3.5+ versions, including the dev ones.
Contents
Documentation
You can find the compiled documentation here:
Installation
Revived package is available on pypi: to install it use the following command:
pip install revived
Examples
Usage examples are coming soon.
Contribute
Clone the repository.
Create the virtualenv.
using virtualenv:
virtualenv ENV bin/activate
using virtualfish:
vf new ENV # optional: automatically load the virtualenv when entering the dir vf connect
Update pip and install pip-tools:
pip install --upgrade pip # pip-tools needs pip==6.1 or higher (!) pip install pip-tools
Install the dependencies:
pip install -r requirements.txt
Build the documentation:
cd docs make html # or whatever format you prefer
Work on the revived module. This project uses pip-tools so you want to add your new direct dependencies in requirements.in and then compile the requirements.txt using:
pip-compile requirements.in
Write tests.
Run tests:
# to have coverage in command line pytest --cov revived --pep8 revived tests # to have html coverage file in the htmlcov directory pytest --cov revived --cov-report html --pep8 revived tests
Check type hints:
mypy revived tests
Create a pull request.
Profit :)
Changelog
0.1.3 - 2017-02-17
Integrate pip-tools: thanks to Lorenzo Villani for pointing me out to this solution
0.1.2 - 2017-02-16
Add documentation, tests and test coverage
0.1.1 - 2017-02-13
Add subscriber decorator in revived.store.Store
0.1.0 - 2017-02-12
Initial release
Metadata
Release files for revived 0.1.4
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 |
|---|---|---|---|---|
| revived-0.1.4.tar.gz | 10.4 kB | Without provenance | Details for revived-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| revived-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for revived-0.1.4-py3-none-any.whl |
Total release size: 22.4 kB
Release files / revived-0.1.4.tar.gz
| Download URL | revived-0.1.4.tar.gz |
|---|---|
| Size | 10.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
610511a3dcc1d081f3c9f1875f0c3809fdee496431d226b9ef467a2cd701100e
|
|
BLAKE2b-256 checksum How to use checksums |
7d348600c4ab8c3e1cf2d25ebff918111a154ab49e3f78ec296a7f41e3842d2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / revived-0.1.4-py3-none-any.whl
| Download URL | revived-0.1.4-py3-none-any.whl |
|---|---|
| Size | 12.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6f48ae719d625f7abc208cfab628e5a5de91f65d772733af39417e5fe8cb3f3a
|
|
BLAKE2b-256 checksum How to use checksums |
65611a9c26bc5ca9fc1618876ec82e091392b27f185a6c2de54801218661a995
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for revived 0.1.4
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.