Should `--disallow-subclassing-any` be renamed or aliased to match the other 'disallow any' flags?

Open
#5,106 4 comments 0 reactions 1 assignee View on GitHub

@Michael0x2a is already working on this.

Since Jun 3, 2018.

Assessment

This issue has not been assessed yet.

Description

feature topic-disallow-any topic-usability

Currently, we have 6 different flags that, when set, prohibit the use of 'Any' in various places. Five of those flags are written in the form --disallow-any-*. The sixth, --disallow-subclassing-any, is the odd one out. (It predates the other five by about a year.)

Would anybody mind if I added an alias for that flag named --disallow-any-subclassing or --disallow-any-subclass and fixed the documentation so it's grouped with the other five?

Dominant language
Python
Stars
20.6k
Forks
3.3k
Avg merge
1d 18h
Merged PRs (30d)
54

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/mypy

All issues in python/mypy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.