Skip to main content

Dash FullCalendar

A lightweight Dash component library that wraps @fullcalendar/react and exposes all free FullCalendar features to Plotly Dash.


Installation

pip install dash-fullcalendar

Quick start

from dash import Dash, html
import dash_fullcalendar as dcal

app = Dash(__name__)

app.layout = html.Div([
    dcal.FullCalendar(
        id="cal",
        initialView="dayGridMonth",
        editable=True,
        selectable=True,
        events=[
            {"title": "Audit", "date": "2025-08-01"},
            {"title": "Go‑Live", "date": "2025-08-10"},
        ],
    )
])

if __name__ == "__main__":
    app.run_server(debug=True)

Open http://127.0.0.1:8050 in your browser and enjoy a fully interactive calendar.


Repository layout

Path Purpose
dash_fullcalendar/ Python package published to PyPI. Contains generated Dash component classes and pre‑compiled JS/CSS assets (_js_dist, _css_dist).
src/ Raw React source for the wrapper.
package.json, rollup.config.js JS build pipeline (npm run build:all).
usage.py Minimal Dash demo used by tests.
tests/ Integration tests with dash[testing] & pytest.
docs/ Optional screenshots / GIFs shown in this README.
.github/ CI workflows that run tests and publish to PyPI + npm.

Ignored via .gitignore:

  • node_modules/
  • dist/, build/, coverage/

Development

  1. Clone and install dependencies

    git clone https://github.com/YOUR_GH_USERNAME/dash-fullcalendar.git
    cd dash-fullcalendar
    npm install
    python -m venv venv && . venv/bin/activate   # Windows: venv\Scripts\activate
    pip install -r requirements.txt -r tests/requirements.txt
    
  2. Build and run the example

    npm run build:all     # creates dash_fullcalendar/_dash_fullcalendar*.js
    pip install -e .
    python usage.py       # open http://localhost:8050
    
  3. Watch & develop

    In one shell:

    npm start            # rebuild JS on change
    

    In another:

    python usage.py      # auto‑reload Dash
    
  4. Run tests

    pytest -q
    

Contributing

Pull requests welcome! To get a change accepted:

  1. Open an issue first for large changes.
  2. Fork, create a descriptive branch name.
  3. Follow Conventional Commits in your commit messages.
  4. npm test and pytest must pass locally—CI will enforce this.
  5. Submit your PR; a maintainer will review and merge.

License

MIT © 2025 Scott Kilgore

Metadata

Release files for dash-fullcalendar 0.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dash-fullcalendar 0.1.3
File Size Uploaded Provenance Actions
dash_fullcalendar-0.1.3.tar.gz 389.0 kB Without provenance Details for dash_fullcalendar-0.1.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for dash-fullcalendar 0.1.3
File Interpreter ABI Platform Actions
dash_fullcalendar-0.1.3-py3-none-any.whl Python 3 none any Details for dash_fullcalendar-0.1.3-py3-none-any.whl

Total release size: 780.5 kB

Release files / dash_fullcalendar-0.1.3.tar.gz

Download URL dash_fullcalendar-0.1.3.tar.gz
Size 389.0 kB
Tags Source
SHA-256 checksum
How to use checksums
81c87e087c3f14ecb38c50bd80779edbc08cd6666833ecf7aa999c5ef7892f17
BLAKE2b-256 checksum
How to use checksums
ac217348088ce5ba5346bf93854863d6b7eebbda24ed593622600c3e55d391b4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.7

Release files / dash_fullcalendar-0.1.3-py3-none-any.whl

Download URL dash_fullcalendar-0.1.3-py3-none-any.whl
Size 391.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1bb9056f56b13a4832f76a0031744e8837e89cccf023c9f9abdf29311447d558
BLAKE2b-256 checksum
How to use checksums
383438a11bbac2831ee287ae3566135da3f18f86ace596a15d1646510c66d80e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.7

Security for dash-fullcalendar 0.1.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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page