The calendar utility reads events from plain text files and outputs today’s events. The files look something like this:
#include <holiday> #include <birthday> 06/15\tJune 15 Thu\tEvery Thursday. 15\t15th of every month. 05/Sun+2\tsecond Sunday in May (Muttertag) 04/Sun-1\tlast Sunday in April Easter-2\tGood Friday (2 days before Easter) Paskha\tOrthodox Easter
This implementation adds some new features while dropping others, most notably, the date formats are not completely compatible:
# added formats 1999/06/15\tJune 15 1999 1999/06/15*\tJune 15 (usefull for birthdays) 1999/05/Sun+2\tsecond Sunday in May 1999 1999/06/15+2\tJune 15 1999 and every second week since then # removed formats (mostly alternative formats) Jun. 15\t06/15 15 June\t06/15 Thursday\tThu June\t06/01 15 *\t15 May Sun+2\t05/Sun+2 04/SunLast\t04/Sun-1
Metadata
Release files for bsd-calendar 0.0.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 |
|---|---|---|---|---|
| bsd-calendar-0.0.0.tar.gz | 3.7 kB | Without provenance | Details for bsd-calendar-0.0.0.tar.gz |
Release files / bsd-calendar-0.0.0.tar.gz
| Download URL | bsd-calendar-0.0.0.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
258a056c04fb8a5637bfe454dc789074c092eca9b95d24e5f717058dd01b4e91
|
|
BLAKE2b-256 checksum How to use checksums |
729d0a1d33c8a8a8aa6d2330269cbf663db586c078f7b1969e8cecdb801dfea8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for bsd-calendar 0.0.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.