Skip to content

[BUG] Issue running Dash on Google Colab (with proposed solution) #3657

Closed

Description

@leontoddjohnson

Hello!

I was running Dash on Google Colab, and I found that (even after installing dash) the recommended code did not work. It turns out, the default Google Colab environment does not include Dash or comm, and that package looks to be required for it to work. In other words, the comm requirement seems to be causing issues ...

Proposal

  • Adjust/Add documentation on Google Colab to include the Dash/comm package install issue
  • Adjust/Loosen (?) the comm package requirement

Current Example
Right now, this seems to work:

First, install packages:

!pip install dash comm

Then, choose app run option.

app.run(debug=True, jupyter_mode='inline', jupyter_height=800)

# OPTIONAL: create url to open in new tab (requires runtime restart)
# app.run(debug=True, host='localhost', jupyter_mode='external')

Thanks!

Activity

  1. camdecoster commented on Mar 18, 2026

    @camdecoster
    Contributor

    Thanks for the report! The team will take a look when we have time and follow up.

  2. T4rk1n commented on Mar 18, 2026

    @T4rk1n
    Contributor

    Seems like comm is usually included from another dependency, since it's used directly it should be added to requirements/install.txt

  3. leontoddjohnson commented on May 7, 2026

    @leontoddjohnson
    ContributorAuthor

    Hey! Just following up on this. Is the issue that we only need to add comm to this install.txt file?

  4. T4rk1n commented on Jul 17, 2026

    @T4rk1n
    Contributor

    Hey! Just following up on this. Is the issue that we only need to add comm to this install.txt file?

    Yes

  5. leontoddjohnson commented on Jul 17, 2026

    @leontoddjohnson
    ContributorAuthor

    Cool. I'm happy to make the update and do a pull request if that's what you guys prefer!

    I just didn't know if this was an internal fix thing, or if I'd be stepping on toes.

  6. T4rk1n commented on Jul 17, 2026

    @T4rk1n
    Contributor

    Cool. I'm happy to make the update and do a pull request if that's what you guys prefer!

    I just didn't know if this was an internal fix thing, or if I'd be stepping on toes.

    Thanks, that would be appreciated.

  7. leontoddjohnson commented on Jul 17, 2026

    @leontoddjohnson
    ContributorAuthor

    Please see PR! I assumed the dev branch was the best place to make this request for.

  8. T4rk1n commented on Jul 21, 2026

    @T4rk1n
    Contributor

    Fixed by #3903

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions