daybook: reading log for the cli
daybook is a reading log app made for the command-line interface (cli).
Install
pip install daybook
Usage
Adding Reading Log Entries
daybook [-h] [-v] {add,del,books,entries,logs,update,config} ...
usage: daybook add [-h] [-r READER] [-k BOOK_KEY] [-t TITLE] [-a AUTHOR] [-d DATE] [--start START] --end END
optional arguments: -h, --help show this help message and exit
reading log: -r READER, --reader READER
book: -k BOOK_KEY, --key BOOK_KEY this can be used instead of title and author -t TITLE, --title TITLE requires author -a AUTHOR, --author AUTHOR requires title
date: -d DATE, --date DATE
pages: --start START --end END
Deleting Reading Log Entries
usage: daybook del [-h] [-r READER] -e ENTRY_ID
optional arguments: -h, --help show this help message and exit
reading log: -r READER, --reader READER
entry: -e ENTRY_ID, --entry ENTRY_ID
Querying Books
usage: daybook books [-h] [-q QUERY]
optional arguments: -h, --help show this help message and exit -q QUERY, --query QUERY this query returns all books containing this value in their titles, authors, or subtitles
Querying Reading Log Entries
usage: daybook entries [-h] [-r READER] [--from FROM_DATE] [--to TO_DATE]
optional arguments: -h, --help show this help message and exit
reading log: -r READER, --reader READER
date range: --from FROM_DATE --to TO_DATE
Listing Reading Logs
sage: daybook logs [-h]
optional arguments: -h, --help show this help message and exit
Updating Entries, Books, Reading Logs, etc.
usage: daybook update [-h] [-r READER] (-e ENTRY_ID | -b KEY | -l KEY)
optional arguments: -h, --help show this help message and exit -r READER, --reader READER -e ENTRY_ID, --entry ENTRY_ID -b KEY, --book KEY -l KEY, --log KEY
App Settings
usage: daybook config [-h] [--get-default-reading-log] [--set-default-reading-log DEFAULT_READING_LOG]
optional arguments: -h, --help show this help message and exit
reading log: --get-default-reading-log --set-default-reading-log DEFAULT_READING_LOG
Metadata
Release files for daybook 1.0.4
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 |
|---|---|---|---|---|
| daybook-1.0.4.tar.gz | 46.1 kB | Without provenance | Details for daybook-1.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| daybook-1.0.4-py3-none-any.whl | Python 3 | none | any | Details for daybook-1.0.4-py3-none-any.whl |
Total release size: 77.9 kB
Release files / daybook-1.0.4.tar.gz
| Download URL | daybook-1.0.4.tar.gz |
|---|---|
| Size | 46.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c449191819a03f3becda5d4339330a11d70cb2a9268579b1297d5867cddf2b45
|
|
BLAKE2b-256 checksum How to use checksums |
7033f2a2cca5481950531d5c2816340d05cca563afd0f9bb7e39ab39705e3adb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.1 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.12
|
Release files / daybook-1.0.4-py3-none-any.whl
| Download URL | daybook-1.0.4-py3-none-any.whl |
|---|---|
| Size | 31.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d66c4cc8d6dcab4c636bb69665bf3f3cdc1c68d1fd1394b871bd238dfb556268
|
|
BLAKE2b-256 checksum How to use checksums |
065b7009ff57f7982d66fbff85a8fd1bacf2296316eab0b7db5bf18b4dbc4e6a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.1 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.12
|
Security for daybook 1.0.4
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.