Skip to content

Consider making astroid.node.* private #1132

Open
@AWhetter

Description

@AWhetter

If we're taking the time and effort to move the astroid.node_classes and astroid.scoped_nodes modules under astroid.nodes, should we consider making these submodules private? I don't think that this separation really helps users and I've always found it annoying (both as a user and as a maintainer) more than I've found it useful for organisation.
It would also give us the flexibility to move classes around so that we can address the cyclic imports that prevent us from being able to declare __all__ and do wildcard imports at the moment.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions