days-until
This CLI helps you count down to upcoming events. Inspired by year-progress.
Installation and Usage
$ pip3 install days-until
$ days-until --add # The config file will be created the first time you run the program
$ days-until
Options
$ days-until [OPTIONS]
Count down days until events.
Written by Aaron Lichtman. https://github.com/alichtman/days_until
Options:
--add Prompt to add events.
--clean Remove events with end dates that have passed.
--compress Compress output when printing.
--config Print path to config file.
--remove Interactively remove events.
-v, --version Print version and author info.
-h, -help, --help Show this message and exit.
Configuration and Events
days-until reads its configuration from $XDG_CONFIG_HOME/.config/days-until.yaml or ~/.config/days_until.yaml.
The easiest way to add events is with the --add option. If you'd like to add the events manually, they should be in the following format:
event1:
event: "Final Day in Switzerland"
dates:
start: "2019-12-7"
end: "2019-12-20"
The top level keys (event1 in this example) don't matter as long as they're unique. I tend to use event{N}, but anything will work.
eventis a string name for the event.startis the date on from which you'd like progress to be tracked.endis the date of the event.
All dates should be in YYYY-MM-DD format.
To remove entries interactively, use the --remove option.
Metadata
Release files for days-until 0.0.2
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 |
|---|---|---|---|---|
| days_until-0.0.2.tar.gz | 6.7 kB | Without provenance | Details for days_until-0.0.2.tar.gz |
Release files / days_until-0.0.2.tar.gz
| Download URL | days_until-0.0.2.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
687ed82b2507b58c5444aac94a57f729868a2c18208bb9a0f836488a1dfb73ed
|
|
BLAKE2b-256 checksum How to use checksums |
6712c30495759f7349583f1b2bf4ccb05ecdb7d2671feed0d3499bb2da7d38c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.8.3
|
Security for days-until 0.0.2
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.