Skip to content

Warn about --follow-untyped-imports #18249

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Dec 7, 2024
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
more feedback
  • Loading branch information
hauntsaninja committed Dec 7, 2024
commit f65a3f6116e718f3f468d4e9439c773a6c2ddc93
3 changes: 2 additions & 1 deletion docs/source/command_line.rst
Original file line number Diff line number Diff line change
Expand Up @@ -168,7 +168,8 @@ imports.

.. option:: --follow-untyped-imports

This flag makes mypy analyze imports even if missing a py.typed marker or stubs.
This flag makes mypy analyze imports from installed packages even if
missing a :ref:`py.typed marker or stubs <installed-packages>`.

.. warning::

Expand Down
3 changes: 2 additions & 1 deletion docs/source/config_file.rst
Original file line number Diff line number Diff line change
Expand Up @@ -320,7 +320,8 @@ section of the command line docs.
:type: boolean
:default: False

Makes mypy analyze imports even if missing a py.typed marker or stubs.
Makes mypy analyze imports from installed packages even if missing a
:ref:`py.typed marker or stubs <installed-packages>`.

If this option is used in a per-module section, the module name should
match the name of the *imported* module, not the module containing the
Expand Down
Loading