wyattscarpenter

I'm not sure if this bug has subsequently been fixed. Assuming it hasn't, another workaround that might help is `--follow-untyped-imports`. This will try to analyze all the files. They probably...

@HyukjinKwon Sure! Sorry for the delay.

Thanks for mentioning! Reviewing that document, I take this sentence to indicate that this doesn't need a JIRA ticket: > If the change is new, then it usually needs a...

This PR is still good and necessary. To whomever is concerned: it should not be marked stale.

Today I was reminded by some warnings in my terminal that this is still a live issue. I would be pleased if it were merged, although it's ultimately of little...

I think this was probably fixed in another way (removing the backslashes entirely), in August, in v0.31.0, with https://github.com/databricks/databricks-sdk-py/commit/fb30ed98912a4e62a4b535188765f792b7bc6f47#diff-9125abd285f0b94b52f0445f9f85a75a921fae47124d670ab9f8f822de9f33acL6 Hence this pr now has a merge conflict. And, more importantly,...

Seems related to https://github.com/python/mypy/issues/16734, "Enforce [that] conditional values are booleans" ; although the idea of that issue is that every x in if x should actually have the type of...

As I was making this change, and adapting the mypy codebase to include some new stubs, I realized that the requirements.txt files tell you to run `pip-compile --output-file=test-requirements.txt --strip-extras --allow-unsafe...

An interesting mypy_primer diff! We can safely ignore all of the candy stripes where some [import-untyped] just became some [import-untyped-stubs-available]. (Side note: are people just running mypy on these projects...

Ok, since merging there's a new error I need to deal with — maybe related to the reports.test thing? — so it's back to being a draft PR until then....