Skip to content

Create external plugin for popular library brains ? #1312

@Pierre-Sassoulas

Description

@Pierre-Sassoulas

Current behavior

Most brain modules are actually for builtin functions and classes. Those should stay within astroid.

For the external one, if they are simple it's certainly much easier to keep them in astroid directly.

For complex one (like numpy or pandas) there could be an argument to move them to new projects. The package name should probably be something like pylint-numpy as it would be a pylint plugin. The issue then just becomes who will maintain them?

Expected behavior

Well defined criteria and a documented way to create an astroid plugin for a popular and complex library.

See #1298 (comment)

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