Connector calendars is a Django application for tracking third-party calendars via iCalendar feed and syncing events based on that feed. It relies on connector-events for managing individual events themselves.
It was designed as a component for a ‘connector’ project, tracking events for a community from multiple sources.
Documentation
The full documentation is at https://connector-calendars.readthedocs.org.
Quickstart
Install connector-calendars:
pip install connector-calendars
Then add events and calendars to your project’s INSTALLED_APPS:
INSTALLED_APPS = (
'events',
'calendars',
)
After adding calendar feeds in the admin you can update them right from there, or use the read_calendars management command to begin syncing them.
History
0.1.0 (2014-09-01)
First release on PyPI.
Metadata
Release files for connector-calendars 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 | |
|---|---|---|---|---|
| connector-calendars-0.1.0.tar.gz | 7.1 kB | Without provenance | Details |
Release files / connector-calendars-0.1.0.tar.gz
| Download URL | connector-calendars-0.1.0.tar.gz |
|---|---|
| Size | 7.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b34237930ba1eb68c6a215e673a6e653d6517fb684305a48bacbd044878032dc
|
|
BLAKE2b-256 checksum How to use checksums |
44e13535c752d3e2d5faca1c70238ed7da8cda3e42e6988404bb6f568a265514
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for connector-calendars 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.