Document or explain "<nothing>"

Open
#3,030 6 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
devtools

Research direction

Start by tracing where mypy produces the <uninhabited> text for type variables with no constraints, then review the existing documentation for type-variable errors. Done means either the term is clearly explained in the appropriate documentation or the displayed string is replaced with a more self-explanatory one.

Written by the indexing model from the issue text.

Description

documentation priority-1-normal topic-usability

Users can now get <uninhabited> in error messages when there are no constraints on a type variable. This should either be documented somewhere, or we should use a more self-explanatory string to display the type.

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.