@Toxyxer recently fixed #34870. As mentioned:

A great follow-up would be to make this work for

• } braces in
  • object literals
  • interfaces and object type literals
  • namespaces and augmentations
  • jsx expressions
• Parentheses in
  • parenthesized expressions
  • parenthesized types
  • argument lists
  • parameter

Some users don't understand why mypy complains about incompatible overrides. We could add an extra note in cases where the argument type is narrower in an override or the return type is wider (or all incompatible overrides). The note could mention Liskov substitution principle and add a link to mypy documentation (add a new section to https://mypy.readthedocs.io/en/latest/common_issues.html perhap

Issue Scope

1. provide an example in the guided tour on following imports in a virtualenv
2. clarify CLI argument documentation to show how to pass multiple directories to --search-path

The Story

I wanted to write an example of checking pip-installed imports using pyre. After reading through the documentation, I found that vanilla `source activate my-venv; pyre --source-directory

Example annotation:

from typing import overload

@overload
def f(x: str) -> str: ...
@overload
def f(x: int) -> int: ...

and source file

def f(x):
    if isinstance(x, (str, int)):
        return x
    else:
        raise TypeError(f"x should be str or int, got {type(x)}")

Call

merge-pyi foo.py foo.pyi

Actual output

PEP484 allows TypeVar to be used anywhere, not necessarily in Generic classes, see this section.

However as of today the following fails:

from enforce import runtime_validation
from typing import TypeVar, Type

T = TypeVar('T', bound=int)


@runtime_validation
class Foo:
    def foo(self, arg: Type[T]) -> T:
    

It'd be neat to have a top-level tests directory, with a bunch of Pikelet test files in there, and a custom test harness to check them.

There is controversy about how improper list should be treated (see josefs/Gradualizer#110). Explain the stance Hammox takes on this issue.