onecron
sleep until next specified time.
Usage
$ onecron 12:00 --debug 2>/dev/null
[I|16910|200522 10:04:05.773 root:MainThread:onecron:56] Wait for 2020-05-22 12:00:00
^C
$ onecron 0 12 * * * --debug 2>/dev/null
[I|17467|200522 10:04:20.802 root:MainThread:onecron:56] Wait for 2020-05-22 12:00:00
^C
$ onecron 0 12 --debug 2>/dev/null
[I|17717|200522 10:04:30.514 root:MainThread:onecron:56] Wait for 2020-05-22 12:00:00
$ ./onecron 6 10 && echo $(date)
2020年 5月 22日 金曜日 10:06:00 JST
Installation
pip install onecron
Requirements
Compatibility
Licence
Metadata
Release files for onecron 0.1.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 | |
|---|---|---|---|---|
| onecron-0.1.0.tar.gz | 2.6 kB | Without provenance | Details |
Release files / onecron-0.1.0.tar.gz
| Download URL | onecron-0.1.0.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a990996d277ba0ea52af17a2aba8b30fa1d4712e8c73a27e8006a57f154fafaa
|
|
BLAKE2b-256 checksum How to use checksums |
e20411b01e8a57b88b564ee27f18d1680b7e976c02b6614837aa1b7181309110
|
| 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/41.2.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.8.3
|
Security for onecron 0.1.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.