Skip to content

Add import-linter - #3332

Open
deronnax wants to merge 1 commit into
vinta:masterfrom
deronnax:add-import-linter
Open

Add import-linter#3332
deronnax wants to merge 1 commit into
vinta:masterfrom
deronnax:add-import-linter

Conversation

@deronnax

@deronnax deronnax commented Sep 11, 2026

Copy link
Copy Markdown

Project

import-linter

Checklist

  • I read CONTRIBUTING.md - awesome-python is a shortlist, not a catalog
  • One project per PR
  • PR title format: Add project-name
  • Entry format: - [pypi-name](https://github.com/owner/repo) - Description ending with period.
  • Display name is the PyPI package name
  • Placed in an existing use case (new sections and subcategories are maintainer-only)
  • Meets all Quality Requirements: active, stable, documented, at least 1 month old

Which Tier

Pick one:

  • Obvious choice - a tool an experienced Python developer would name when asked "what do I use for this?"
  • Challenger - not yet the obvious choice, but a credible successor to one. Give adoption-trajectory evidence, not popularity alone.

Explain:

Project is now more than 5 years old. I did not use it but that's what we wished we had at GitGuardian. If you don't feel the suggestion relevant, feel free to close.

A 2019 PR (#1428) was closed under the old vote threshold, not a quality rejection.

Displacement

If the use case is at its cap, name the entry your project replaces and argue that yours does that entry's job better. One in, one out.

None. Code Analysis currently has 4 entries (cap 5).

Place it in Code Analysis as a challenger for architectural import
constraints, filling the remaining slot without displacement.
@deronnax deronnax mentioned this pull request Sep 11, 2026
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant