calendar-cli
Command-line Interface for Google Calendar
Dependencies
Python: 2.6 / 2.7
six
python-dateutil
pytz
tzlocal
google-api-python-client
argparse
Installation
pip command may need sudo
Operation |
Command |
|---|---|
Install |
pip install gcalendar-cli |
Upgrade |
pip install --upgrade gcalendar-cli |
Uninstall |
pip uninstall gcalendar-cli |
Check installed version |
calendar-cli --version |
Help |
calendar-cli -h |
Getting Started
Download client_secret.json from Google Developers Console
Open Google API Manager
Select or create a project
Open API Manager -> Credentials
OAuth consent screen: Set a product name and save
Credentials: Add credentials -> OAuth 2.0 client ID -> Other: Set a name and create
Download a credential file by clicking the Download JSON button, then rename it client_secret.json
Create a credentials file
calendar-cli setup client_secret.json
The default path to the credentials file is ~/.credentials/calendar-cli.json.
Print the summary of today’s events on the default calendar
calendar-cli
Launch with arguments
calendar-cli --date 20151014 calendar-cli --calendar xxxxxx@group.calendar.google.com
1 maintainer
Metadata
1 maintainer
Release files for gcalendar-cli 0.2.3
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 |
|---|---|---|---|---|
| gcalendar-cli-0.2.3.tar.gz | 8.8 kB | Without provenance | Details for gcalendar-cli-0.2.3.tar.gz |
Release files / gcalendar-cli-0.2.3.tar.gz
| Download URL | gcalendar-cli-0.2.3.tar.gz |
|---|---|
| Size | 8.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c78402f45e45c295a418d4d9fb7cb0fc406007f7f7c49d7409802c3f66614872
|
|
BLAKE2b-256 checksum How to use checksums |
3ea79bdc93ce57207633b119999e2ed22c1786c51cdf3da598dd5d7f86c36d28
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for gcalendar-cli 0.2.3
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.
