Skip to content

Widespread mypy failures #143

Closed
Closed
@jaraco

Description

As mentioned in #136 (comment) and #142 (comment), I'm trying to figure out a strategy for incorporating stricter settings for mypy without incurring too much toil.

Right now, about half of the projects are failing:

image

  • jaraco.collections
  • jaraco.compat
  • jaraco.context
  • jaraco.crypto
  • jaraco.desktop
  • jaraco.email
  • jaraco.fabric
  • jaraco.financial
  • jaraco.functools
  • jaraco.home
  • jaraco.imaging
  • jaraco.input
  • jaraco.logging
  • jaraco.media
  • jaraco.modb
  • jaraco.mongodb
  • jaraco.net
  • jaraco.nxt
  • jaraco.office
  • jaraco.parables
  • jaraco.pmxbot
  • jaraco.postgres
  • jaraco.services
  • jaraco.site
  • jaraco.test
  • jaraco.text
  • jaraco.tidelift
  • jaraco.translate
  • jaraco.ui
  • jaraco.util
  • jaraco.vcs
  • jaraco.windows
  • jaraco.xkcd
  • keyrings.alt
  • keyrings.firefox
  • lpaste
  • nat-pmp
  • nspektr
  • openpack
  • paradocx
  • path
  • pip-run
  • pmxbot.webhooks
  • pytest-checkdocs
  • pytest-enabler
  • pytest-perf
  • recapturedocs
  • rst.linker
  • singledispatch
  • svg.charts
  • tempora
  • treehouse
  • xlsxcessive

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions