toggl2cal
My tool that exports toggl as webcal file that I serve from my server.
Install:
$ pip3 install toggl2webcal --user
Readme
usage: toggl2webcal [-h] [-d DAYS] [--no-import] [--no-export] [-o OUT]
token database
Export toggl data to webcal file
positional arguments:
token Toggl token
database SQL alchemy database connector
optional arguments:
-h, --help show this help message and exit
-d DAYS, --days DAYS number of days to look back
--no-import Don't run import from toggl
--no-export Don't run export to webcal
-o OUT, --out OUT output path for the webcal file
Example
toggl2webcal TOGGL_TOKEN sqlite:///time.sqlite
toggl2webcal TOGGL_TOKEN postgresql://myself@localhost
Metadata
Release files for toggl2webcal 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 | Actions |
|---|---|---|---|---|
| toggl2webcal-1.0.tar.gz | 3.3 kB | Without provenance | Details for toggl2webcal-1.0.tar.gz |
Release files / toggl2webcal-1.0.tar.gz
| Download URL | toggl2webcal-1.0.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d331bb5d2a41e1b35b52b5b722a58b28daeb1bb36a04574a6efdf5c8eef1adff
|
|
BLAKE2b-256 checksum How to use checksums |
383d9e4be2056ac2bbeeec9eb64bc775ff26a6e246b3db8c401852bdcd5f80b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.6.8
|
Security for toggl2webcal 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.