_ __ _ __
_ ___ ____ __ ______ ______/ /_____/ /___
_ _ / \/ __ \/ / / /__ \/ ___\, / __ \, /__ \
_ _ / /\/ /_/ /\ \/ / /_/ /\__, / / /_/ / / /_/ /
_ \/ _\__/\/ _\__/ ,___/\____/\/\__/\/\/ ,___/
_____ _ _\____/ _ _\____/
/_ _\
0> 0>
\__⊽__/ (C) Roboy 2018
⋂
About
Ravestate is a reactive library for real-time natural language dialog systems.
Dependencies
portaudio on macOS
In order to install PyAudio with pip, you need to install portaudio first using:
brew install portaudio
Installation
Via PIP
The easiest way to install ravestate is through pip:
pip install ravestate
For developers
First, install dependencies:
pip install -r requirements.txt
# To run tests, install pytest, mocking, fixtures...
pip install -r requirements-dev.txt
Then, you may open the repository in any IDE, and mark the
modules folder as a sources root.
Running Hello World
Ravestate applications are defined by a configuration, which specifies the ravestate modules that should be loaded.
To run the basic hello world application, run ravestate with a config file or command line arguments:
Running with command line spec
You can easily run a combination of ravestate modules in a shared context,
by listing them as arguments to the rasta command, which is installed
with ravestate:
rasta ravestate_conio ravestate_hello_world
Run rasta -h to see more options!
Running with config file(s)
You may specify a series of config files to configure ravestate context, when specifying everything through the command line becomes too laborious:
# In file hello_world.yml
module: core
config:
import:
- ravestate_conio
- ravestate_hello_world
Then, run rasta with this config file:
rasta -f hello_world.yml
Running tests
If you have installed the dependencies from requirements-dev.txt you
may run the ravestate test suite as follows:
./run_tests.sh
Metadata
Release files for ravestate 0.2.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 |
|---|---|---|---|---|
| ravestate-0.2.0.tar.gz | 24.5 kB | Without provenance | Details for ravestate-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ravestate-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for ravestate-0.2.0-py3-none-any.whl |
Total release size: 59.8 kB
Release files / ravestate-0.2.0.tar.gz
| Download URL | ravestate-0.2.0.tar.gz |
|---|---|
| Size | 24.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c2b8300a7da94ca398e786f9433f68fe6856390e68c1948d4e44ba2d9cb04e6a
|
|
BLAKE2b-256 checksum How to use checksums |
0702fbc77dbcc453707c9e5e257caf15fdda71c3ee1efcb71ab96f3a6aa40656
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.7
|
Release files / ravestate-0.2.0-py3-none-any.whl
| Download URL | ravestate-0.2.0-py3-none-any.whl |
|---|---|
| Size | 35.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8034fa4516beaa224b8526f861f3b8c4981557e44930d6d8cf9675f19ef77314
|
|
BLAKE2b-256 checksum How to use checksums |
e6a411a6e9438459e6d04a12f9d2f5ffad30f1461dc8724d5d5b0b445a98ff79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.7
|
Security for ravestate 0.2.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.