python / python/mypy

Difference between the command output and the html report

Open
#14,297 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
20.6k
Forks
3.3k
PR merge metrics
PR metrics pending

Description

Bug Report
When I run mypy I see the following result:
Generated HTML report (via XSLT): C:\Users\jcmencia\PycharmProjects\QA\py_requests\reports\typing\index.html Success: no issues found in 10 source files

But in the html report I get the following line:
self.assertEqual(first=self.__response_data.__str__(), second="RESPONSE", msg="Error verifying Response DTO in a readable format - Incorrect Values")

  • Any Types on this line: Explicit (x3)

Is this an expected behavior or as I think it is a bug?

Environment

  • Mypy version used: 0.991
  • Mypy command-line flags: any flag
  • Mypy configuration options from mypy.ini (and other config files): pyproject.toml
    [tool.mypy]
    html_report = "reports/typing"
    files = "src,tests"
    disallow_any_generics = true
    disallow_incomplete_defs = true
    disallow_untyped_decorators = true
    disallow_untyped_defs = true
    disallow_untyped_calls = true
    disallow_subclassing_any = true
    check_untyped_defs = true
    no_implicit_optional = true
    show_error_codes = true
    warn_redundant_casts = true
    warn_return_any = true
    warn_unused_configs = true
    warn_unused_ignores = true
    warn_unreachable = true
    strict_equality = true
    strict_concatenate = true
  • Python version used: 3.10.9 and 3.11.1

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.

Research direction

Reproduce the report using the provided pyproject.toml settings, the src and tests file set, and mypy 0.991 with Python 3.10 or 3.11. Compare the terminal success message with reports/typing/index.html and determine whether the reported explicit Any entries should be reflected in command output; done means the behavior is explained or covered by a focused regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.