SlapPy
SlapPy is the Python support and generation code for Slapp and Dola. Code on Github.
Requirements
- Python 3.9+
- Create a
.envin the repository root with the following values:
# Required values:
# Source address for Battlefy backend
CLOUD_BACKEND="https://xxxxx.cloudfront.net"
# Path to SplatTagConsole for Slapp things
SLAPP_CONSOLE_PATH=".../SplatTagConsole.dll"
# Path to the Slapp App Data folder
SLAPP_DATA_FOLDER=".../SplatTag"
# Optional values depending on requirements:
# Database variables if using the database, which are:
DATABASE_HOST="localhost:5000"
DATABASE_NAME="database"
DATABASE_USER="user"
DATABASE_PASSWORD="user"
# A Discord bot token if using the backtrace:
BOT_TOKEN="xxxxxx.xxxxxx.xxxxxx"
# Challonge credentials if using Challonge downloaders
CHALLONGE_API_KEY="xxxx"
CHALLONGE_USERNAME="YourUsername"
# Smash GG credentials if using Smash GG downloaders
SMASH_GG_API_KEY="xxxx"
Distribution
Up-version by changing setup.py.
The following commands should be entered into the venv console:
Windows:
rmdir /S build
rmdir /S dist
py -m pip install --upgrade build
py -m build
py -m pip install --upgrade twine
py -m twine upload dist/*
Linux:
rm -r build
rm -r dist
python3 -m pip install --upgrade build
python3 -m build
python3 -m pip install --upgrade twine
python3 -m twine upload dist/*
Updating the Database
new_sources_file.py has the steps broken down to generate new sources from scratch. The main code will look something like:
if __name__ == '__main__':
import dotenv
import logging
from slapp_py.misc.new_sources_file import full_rebuild
# Load the environment variables as listed above, populated into the .env file
dotenv.load_dotenv()
# And setup logging.
logging.basicConfig(level=logging.INFO)
# To generate the new sources file, where the parameter is skipping pauses.
# If pauses are skipped, patching the database is assumed.
# In 'False' mode, the script will ask.
full_rebuild(False)
Metadata
Release files for SlappPy-Slate 1.14.7
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 |
|---|---|---|---|---|
| SlappPy-Slate-1.14.7.tar.gz | 63.6 kB | Without provenance | Details for SlappPy-Slate-1.14.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| SlappPy_Slate-1.14.7-py3-none-any.whl | Python 3 | none | any | Details for SlappPy_Slate-1.14.7-py3-none-any.whl |
Total release size: 148.4 kB
Release files / SlappPy-Slate-1.14.7.tar.gz
| Download URL | SlappPy-Slate-1.14.7.tar.gz |
|---|---|
| Size | 63.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e46d9a287f804be8dc4c518cfe10ccc8237f5cb0f92980d9f487dc1b24a68965
|
|
BLAKE2b-256 checksum How to use checksums |
0dba54b96692faba259b76bdd863aa0beaf0dc0b30141a9aaa40dd14d4a8cc11
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.0.1 pkginfo/1.8.2 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.7
|
Release files / SlappPy_Slate-1.14.7-py3-none-any.whl
| Download URL | SlappPy_Slate-1.14.7-py3-none-any.whl |
|---|---|
| Size | 84.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b70f3a20c742ebd25d428f3656a8caed95d8e5deba68b3db22daf903b6340628
|
|
BLAKE2b-256 checksum How to use checksums |
ba2ec4f9ae83c1c862bba35abc89d7a9c4c2a4c335005b536eac1440f58d9a97
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.0.1 pkginfo/1.8.2 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.7
|
Security for SlappPy-Slate 1.14.7
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.