Gregory P. Smith

The problem I have with allowing `Sequence[str]` or `Iterable[str]` to be satisfied by `str` is that the problem of passing a `str` in where a sequence of (generally non single...

Given the norm for most APIs is to accept the iterable and never want plain `str` we should aim to support that as a trivial annotation that doesn't involve multiple...

> _In short: is passing a str as an Iterable[str] a common error?_ Yes. We have seen this specific bug multiple independent times at work. Unfortunately more than once after...

FWIW pytype just gained a new behavior: """ As of early August 2021, Pytype introduced a check that forbids matching str against the following types to prevent a common accidental...

> The typing-sig@ mailing list a focused on discussing improvements to Python static typing. Recommendation for all: Join the list and make this not be true. That statement is merely...

a similar place that could use parens: ``` if some_var.check_thing() and some_long_boolean_var and another_long_boolean_var: pass ``` currently that formats to this oddity: ``` if some_var.check_thing( ) and some_long_boolean_var and another_long_boolean_var:...

Internally I do see one recent user contributed library that implements its own `DEFINE_path` for use with `absl`. The gist of that goes something like this _(simplified for illustration purposes)_...

We're tentatively accepting the PEP by telling the next SC to do so in three months in absence of new compelling reasons not to. See https://discuss.python.org/t/pep-649-deferred-evaluation-of-annotations-tentatively-accepted/21331 for what that means...

> Your PR has a conflict. Please resolve the conflict first to get merged Nope. See the comment above. this change was already applied.

@shicks & @dseomn looks like you added the apache 2.0 LICENSE file to the styleguide repo in 2020. the existing README said creative commons. could you clarify this?