Skip to content

resolve the import cycle warnings #149

@keewis

Description

@keewis

As described in #143, sphinx has started to emit "import cycle" warnings when using an absolute import while currentmodule is active. This means that packages that define both the object that is extended and any accessors will see this warning.

In #143 I chose to ignore the warning, but it would still be better to resolve it instead (somehow).

Metadata

Metadata

Assignees

No one assigned

    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