CycloMonitor
Command-line tool and Discord bot which presents ATCF and Best Track data.
Dependencies:
- aiohttp (provided by py-cord)
- py-cord (Optional, for running the bot)
- tendo (Optional, for running the bot)
Disclaimer
No party involved with CycloMonitor should make any claim that this program is intended to replace tropical cyclone advisories/warnings issued by your local RSMC or TCWC. If you need more detailed information than what is provided by the program, see your local RSMC or TCWC website for forecasts, potential land impacts, or other relevant information.
Running interactively
Install the package:
pip install cyclomonitor
Start an interactive session:
python3 -m cyclomonitor -i or python3 -m cyclomonitor.cli
When running interactively, type help to see available commands.
Running the bot
Install the package with everything needed to run the bot:
pip install cyclomonitor[bot]
If you cloned the GitHub repository, you might want to install the package in dev mode:
cd cyclomonitor
pip install -e .[bot]
Some Linux distributions may require you to set up a virtual environment.
Until I get the project to use absolute paths, you'll probably want to create a separate directory to store its data:
mkdir cyclomonitor_temp
cd cyclomonitor_temp
To run the bot:
python3 -m cyclomonitor -b -t your.token.here
If you don't want to specify -t every time, paste your bot's token into a file called TOKEN in your working directory.
For full argument list: python3 -m cyclomonitor -h or run the module with no arguments.
Windows users: You might want to replace python3 with python.
If you're using a virtual environment, ensure it is active before running the bot.
CycloMonitor logs to stdout by default. To log to a file, specify the parameter -l LOGFILE, where LOGFILE is the path to the log file.
Configuring the bot
See CONFIGURATION.md for details.
Supports Python 3.8+, but Python 3.11+ is recommended.
Metadata
Release files for cyclomonitor 2025.7.17
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 |
|---|---|---|---|---|
| cyclomonitor-2025.7.17.tar.gz | 69.2 kB | Without provenance | Details for cyclomonitor-2025.7.17.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cyclomonitor-2025.7.17-py3-none-any.whl | Python 3 | none | any | Details for cyclomonitor-2025.7.17-py3-none-any.whl |
Total release size: 152.3 kB
Release files / cyclomonitor-2025.7.17.tar.gz
| Download URL | cyclomonitor-2025.7.17.tar.gz |
|---|---|
| Size | 69.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6aa162050054c717d4d11c4a5ac58dc5b1cc7e87f377cf4b0f688b3417e19a1b
|
|
BLAKE2b-256 checksum How to use checksums |
17e8a51428804dd855a18f42853f2d02579d7f61f0ba97cda8dac15274d6b759
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.5
|
Release files / cyclomonitor-2025.7.17-py3-none-any.whl
| Download URL | cyclomonitor-2025.7.17-py3-none-any.whl |
|---|---|
| Size | 83.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1ac8ad46af92a97ec4e3e5d80d54b5f371391a52f9d67b26f85163585bb28557
|
|
BLAKE2b-256 checksum How to use checksums |
a06476d537655b7f2238b0c2c38e08f73e6fa170a92b1454e1429d66749d7f28
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.5
|
Security for cyclomonitor 2025.7.17
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.