This release is a pre-release and may not be stable for production use.
Discord REPL
A discord bot to run code in containers.
Development
Requirements
- python 3.10
- docker
Install pipenv
python -m pip install --user pipenv
Prepare the environment
pipenv install --dev
Run the tests
pipenv run test
Running the bot
First of all you will need to create a application/bot on discord. Here are some usefully links:
Get your bot token and add it to .env or as variable when running the bot.
Using .env.
Add to the .env
echo "DISCORD_TOKEN=... >> .env
Run the bot
pipenv run bot
Take care of your token, don't commit it.
Using as variable
DISCORD_TOKEN=... pipenv run bot
Metadata
Release files for discord-repl 0.0.dev1669116664
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 |
|---|---|---|---|---|
| discord-repl-0.0.dev1669116664.tar.gz | 8.5 kB | Without provenance | Details for discord-repl-0.0.dev1669116664.tar.gz |
Release files / discord-repl-0.0.dev1669116664.tar.gz
| Download URL | discord-repl-0.0.dev1669116664.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
408084c55d6a2e69d375aa1a30cbee84c6f5a0aa67f0b7541ea14282509fa67c
|
|
BLAKE2b-256 checksum How to use checksums |
c71ac90d36b61bb69399dee9678fc2aacee5ce85625616bd10f1cd82e4e8bec2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.8
|
Security for discord-repl 0.0.dev1669116664
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.