rewardify-base
Base frame reward system
Free software: BSD license
Documentation: https://rewardify-base.readthedocs.io.
Features
TODO
Credits
This package was created with Cookiecutter and the audreyr/cookiecutter-pypackage project template.
History
0.0.0 (2019-06-08)
First release on PyPI.
0.1.0 (2019-06-14)
Initial version
0.1.1 (2019-06-14)
Fixed bug in setup.py, which caused the “backends” package to be excluded
0.2.0 (2019-06-15)
Internal changes in the recycle method for rewards
Added a “user_exists” method to the facade, which will return, whether or not the given user name exists in the database or not
- Added “effect” field to Reward class
An optional string item “effect” can ba added to the config of any reward. This string should contain special syntax, for what effect the reward usage should have on the rewardify system
Currently granting the user gold and dust are supported effects
Added more methods for handling rewards to the facade, which include buying, using and recycling rewards
0.2.1 (2019-06-16)
Fixed, that the facade method for buying a pack internally called the method for adding a pack, thus not actually spending gold on it
0.2.2 (2019-06-16)
Added “user.save()” calls to all the methods of the facade, that modify the models, so that the modifications actually get taken over into the database
0.2.3 (2019-06-16)
Extended the clean method for the Environment setup of the test cases to also remove sub folders
0.2.4 (2019-06-16)
Fixed a bug, which causes the “open_pack” method of the User model not to work properly
0.2.5 (2019-06-16)
Rethought the effect system: The “use” method of Reward now returns a list with functions, which contain the effects.
Fixed a bug, where the facade method for using a reward did not execute the effects of the reward properly
0.2.6 (2019-06-16)
Changed the install directory for linux from “~/.rewardify” to “/opt/.rewardify” as the previous one isnt working with python path handling.
0.2.10 (2019-06-16)
Added a method “init” to the EnvironmentConfig singleton, which will create the connection to the database
0.2.11 (2019-06-16)
Fixed, that the pointer to the last accounted action was not being saved within the ForestBackend
0.2.12 (2019-06-16)
Fixed the gold evaluation for the reward effects, it was accidentally set to constant value
Metadata
Release files for rewardify 0.2.12
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 | |
|---|---|---|---|---|
| rewardify-0.2.12.tar.gz | 54.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rewardify-0.2.12-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 96.0 kB
Release files / rewardify-0.2.12.tar.gz
| Download URL | rewardify-0.2.12.tar.gz |
|---|---|
| Size | 54.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0800dcd53c68440b2d5257d3f743c279e874758c72b5fa9a747406cc9dc3260c
|
|
BLAKE2b-256 checksum How to use checksums |
4672b4aa4eb7ec3be9736641e5ca4885e392d68e517942dedc4a882eab1238e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.6.7
|
Release files / rewardify-0.2.12-py2.py3-none-any.whl
| Download URL | rewardify-0.2.12-py2.py3-none-any.whl |
|---|---|
| Size | 41.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
99039ea4a451b543e7b282d477cb441cb03cb25091c508b334cc3ed31697621e
|
|
BLAKE2b-256 checksum How to use checksums |
3697fce207a48e7d7b85a0b1a8f6cfc4e0729341f6bed407b7c009d747e097a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.6.7
|
Security for rewardify 0.2.12
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.