Skip to content

RedisIntegration does not throw DidNotEnable when there is no redis module #735

@soutys

Description

@soutys

Most of integrations have ModuleDoesNotExist / ImportError try...except block throwing DidNotEnable exception (see: celery, flask, sqlalchemy).

RedisIntegration have redis module import inside setup_once method because of monkey-patching.

This causes some sort of problems during wide-range integrations autodetection.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions