# Luthor for Amazon Lex - Multi-Bot Manager and Player
# Overview Typically, the goal of a Lex conversation is to fulfill a single set of intents, however, there are use cases where a conversation may need to temporarily change topics.
For example, in the case of someone with special needs, a person may be in the middle of a Lex conversation ordering their lunch through the LunchBot, and then suddenly ask a completely irrelevant question which maybe handled by the CommonQuestionBot. Luthor for Lex can switch contexts to the question bot, and then naturally transition back to the original bot. This provides a “[stream of consciousness](https://en.wikipedia.org/wiki/Stream_of_consciousness “stream of consciousness”)” flow to the conversation.
Luthor for Lex allows you to run multiple simultaneous bots, switching contexts and managing the transition between bots cleanly and naturally.
# Features * Create/update bots, slots and intents using YAML (transparently handles checksums) * Run multiple bots at the same time within a single conversation * Event hook model for each bot provides several points of customization * Customizable transitions between bots to provide a natural conversation flow * Built-in bot player, using audio or keyboard entry
Metadata
Release files for luthor-for-lex 0.0.16
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 |
|---|---|---|---|---|
| luthor-for-lex-0.0.16.tar.gz | 19.0 kB | Without provenance | Details for luthor-for-lex-0.0.16.tar.gz |
Release files / luthor-for-lex-0.0.16.tar.gz
| Download URL | luthor-for-lex-0.0.16.tar.gz |
|---|---|
| Size | 19.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b5a8f5597db23758a82df2cf01948caf8d41e66d370dd21f3e7175ab230a6e73
|
|
BLAKE2b-256 checksum How to use checksums |
9efe36cb3dc748a1667e5f2e6e438590fc25b649e554d7ef4a95ad98bcaf0d69
|
| 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.2.0 requests-toolbelt/0.9.1 tqdm/4.35.0 CPython/3.7.4
|
Security for luthor-for-lex 0.0.16
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.