periodical_requests_recorder
Usage
periodical_recorder example.yaml
yaml data format example.
gmail_address: example@gmail.com
gmail_oauth: "~/yagmail_secret.json"
tasks:
-
name: "some_data"
url: "https://example.com/somedata.csv"
record_dir: "~/hist_data/"
output_file_format: "{name}/{name}_%Y-%m-%d.csv"
cron_expr: "0 * * * * * *"
encoding: "ms932"
-
name: "some_data_2"
url: "https://www.google.com/"
record_dir: "~/hist_data/"
output_file_format: "{name}/{name}_%Y-%m-%d.txt"
cron_expr: "@reboot"
target_elements:
-
element: "#gws-output-pages-elements-homepage_additional_languages__als"
index: 3
Request result will be stored in the record_dir with your output_file_format.
If you set up yagmail, error messages will be sent to your address.
cron_expr format is the same as Crython.
Installation
You can install this with pip.
Requirements
Compatibility
Licence
periodical_requests_recorder was written by fx-kirin.
Metadata
Release files for periodical-requests-recorder 0.4.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 |
|---|---|---|---|---|
| periodical_requests_recorder-0.4.0.tar.gz | 5.1 kB | Without provenance | Details for periodical_requests_recorder-0.4.0.tar.gz |
Release files / periodical_requests_recorder-0.4.0.tar.gz
| Download URL | periodical_requests_recorder-0.4.0.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
61be5b1817a9163c6b1a081f52093a903cc675fe6d067baf72d2ecc3171a3511
|
|
BLAKE2b-256 checksum How to use checksums |
0675f3a06ba1511dc0953952f403c167db1c5d9918c51fc1c3e55f958479ab5b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.4
|
Security for periodical-requests-recorder 0.4.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.