Sopel plugin .in command:
[17:30] Exirel: .in 2h go to the grocery store [17:30] Sopel: Exirel: I will remind you that at 2023-10-13 -19:30:00CEST (... 2h later ...) [19:30] Sopel: Exirel: go to the grocery store
And .at command:
[17:30] Exirel: .at 19:30 go to the grocery store [17:30] Sopel: Exirel: I will remind you that at 2023-10-13 -19:30:00CEST (... 2h later ...) [19:30] Sopel: Exirel: go to the grocery store
The .in command accepts time units ranging from days to seconds:
.in 1d2h In one day and 2 hours .in 2h59m3s In 2 hours, 59 minutes, and 3 seconds
The .at command is timezone aware, and tries to use the timezone set for the user. If not found, it will use the timezone set for the channel. If none is set, it will assume UTC+0.
When using .at with a past hour, the command will assume tomorrow instead of today: setting a reminder for 9 a.m. when it’s 10 a.m. will create a reminder for 9 a.m. tomorrow.
You can also use a date instead of a time, or you can use both, placed before or after the time:
.at 2023-06-27 Python 3.7 EOL .at 12:00 2023-06-27 Python 3.7 EOL .at 2023-06-27 12:00 Python 3.7 EOL
Passing only a date will set a reminder on that date with the current time (not adjusted for summer/daylight-savings).
Install
The recommended way to install this plugin is to use pip:
$ pip install sopel-remind
Note that this plugin requires Python 3.7+ and Sopel 7.1+. It won’t work on Python versions that are not supported by the version of Sopel you are using.
Migration from built-in
If you used Sopel 7.1 (or any previous version) and its built-in “remind” plugin, you may want to migrate your reminders to the new plugin. To do that, you can run the sopel-plugins configure remind command and allow the script to perform the migration. This will import the reminders from the original file before renaming it (by adding the .bk suffix).
Metadata
Release files for sopel-remind 0.3.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 |
|---|---|---|---|---|
| sopel-remind-0.3.0.tar.gz | 14.3 kB | Without provenance | Details for sopel-remind-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sopel_remind-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for sopel_remind-0.3.0-py3-none-any.whl |
Total release size: 24.2 kB
Release files / sopel-remind-0.3.0.tar.gz
| Download URL | sopel-remind-0.3.0.tar.gz |
|---|---|
| Size | 14.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
21ae0105da5864ee756baa87fe01d92233f28b8526ac741581a41722810753d1
|
|
BLAKE2b-256 checksum How to use checksums |
910ddf3ec8d0def90b190f83557cbde5aba6c985a608ce5aca6e9bbfd5a21746
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Release files / sopel_remind-0.3.0-py3-none-any.whl
| Download URL | sopel_remind-0.3.0-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cbd317b2a01794f1fc0bd5ee1558024ff9bcdd601f578554c8ee2bf36f6063b1
|
|
BLAKE2b-256 checksum How to use checksums |
217d20c990389148a1a9e8fb299fbb78dbef7449b0dc7291c3b51aa5cf3bdf31
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for sopel-remind 0.3.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.