Mailman 3 January 2023 - Typing-sig

Opened and changed typing issues week 2023-W03
by Typing Bot Jan. 23, 2023

Jan. 23, 2023

The following is an overview of all issues and pull requests in the typing repository on GitHub with the label 'topic: feature' that were opened or updated last week, excluding closed issues. --------------------------------------------------- The following issues and pull requests were updated last week: #566 AnyOf - Union for return types opened by @srittau https://github.com/python/typing/issues/566 --------------------------------------------------- All issues and pull requests with the label 'topic: feature' can be viewed under the following URL: https://github.com/python/typing/issues?q=label%3A%22topic%3A+feature%22

1 0

PEP 702: Marking deprecations using the type system
by Jelle Zijlstra Jan. 22, 2023

Jan. 22, 2023

I just posted PEP 702, Marking deprecations using the type system: https://peps.python.org/pep-0702/. The PEP proposes adding an @typing.deprecated() decorator to mark classes, methods, and functions as deprecated. Type checkers will leverage this decorator to inform users about their usage of deprecated features. I welcome feedback on any aspect of the proposal. However, two main points came up in initial discussions: - The proposal specifies that the decorator does not raise any runtime DeprecationWarning. Should we change this, perhaps with an opt-in flag? - The proposal allows users to mark classes, functions, and overloads as deprecated, but there are other things that may want deprecation. Should we add support for deprecating modules, or variables, or parameters? Happy New Year!

5 5

Opened and changed typing issues week 2023-W02
by Typing Bot Jan. 16, 2023

Jan. 16, 2023

The following is an overview of all issues and pull requests in the typing repository on GitHub with the label 'topic: feature' that were opened or updated last week, excluding closed issues. --------------------------------------------------- The following issues and pull requests were updated last week: #213 Introduce an Intersection opened by @ilevkivskyi https://github.com/python/typing/issues/213 #256 Possible to distinguish between Sequence[str]/Iterable[str] and str? opened by @jtatum https://github.com/python/typing/issues/256 #801 Introduce a Not type opened by @antonagestam https://github.com/python/typing/issues/801 --------------------------------------------------- All issues and pull requests with the label 'topic: feature' can be viewed under the following URL: https://github.com/python/typing/issues?q=label%3A%22topic%3A+feature%22

1 0

Extending LiteralString or Literal with structural validation
by Mathew Elman Jan. 9, 2023

Jan. 9, 2023

I actually posted this in python-ideas and I was quickly suggested to come here instead: """ It would be useful to take advantage of the `LiteralString` or `Literal` type hints to add structural validation to literals. For *example*, if these could be subclassed to add a validation method: class MyLiteral(LiteralString): def __validate__(self): ... or extended to allow something like regex in there generic type parameter: Literal[r"\w+"] LiteralString[r"\w+"] then specific kinds of literal string can be "enforced" by static type checkers. Then IDEs could at the very least highlight that a string literal is not valid. I stress these are just examples, the goal is to have a way to tell a static type checker what the structure of a string literal has to be. """

2 2

Opened and changed typing issues week 2023-W01
by Typing Bot Jan. 9, 2023

Jan. 9, 2023

The following is an overview of all issues and pull requests in the typing repository on GitHub with the label 'topic: feature' that were opened or updated last week, excluding closed issues. --------------------------------------------------- The following issues and pull requests were opened last week: #1329 Inferring keyword arguments from attributes opened by @GideonBear https://github.com/python/typing/issues/1329 --------------------------------------------------- The following issues and pull requests were updated last week: #566 AnyOf - Union for return types opened by @srittau https://github.com/python/typing/issues/566 --------------------------------------------------- All issues and pull requests with the label 'topic: feature' can be viewed under the following URL: https://github.com/python/typing/issues?q=label%3A%22topic%3A+feature%22

1 0

Re: PEP 702: Marking deprecations using the type system
by ItsDrike Jan. 2, 2023

Jan. 2, 2023

I would say that supporting deprecation for variables should absolutely be a part of this PEP, but it might not actually require a `typing.Deprecated` modifier like suggested in the rejected ideas, and instead we probably could get away with just use the `typing.deprecated`, which would simply mark it internally for the type-checker as a deprecated utility, but the call itself would just return the same value. So this could look like: `X = typing.deprecated("Constant moved to module.foo")(5)`, or to make this a bit easier for this kind of use,there could be a special case handling for 2 argument version of `typing.deprecated`, which would then look like: `X = typing.deprecated("Constant moved to module.foo", 5)`. That said, `typing.Deprecated` as suggested would probably be more consistent with the rest of the type system, but if the rejection was done purely to avoid adding yet another typing modifier that breaks forward references, this could be a solution that avoids it. The reason I think this should be supported is because in some cases, typed libraries might have some commonly used type alias that now needs to be renamed or moved elsewhere. Without a way to deprecate constants, this is completely impossible, not just on type checking time, but also on runtime, as this is just a type alias imported as a simple constant, so there's no easy way to emit a warning on runtime for such use, forcing the library to make an unexpected breaking change. I'd say that there should absolutely be some support in the typing system that allows typed libraries to safely get rid of a type alias, with a deprecation period. This is a bit more complicated with simple constants though, which this absolutely should work for too, however constants are likely gonna be used in non-typed environments too, and since this kind of deprecation won't actually cause any runtime warnings, people not using a type-checker might still end up facing an unexpected breaking change. I don't see any easy way to address this though.

3 2

Opened and changed typing issues week 2022-W52
by Typing Bot Jan. 2, 2023

Jan. 2, 2023

The following is an overview of all issues and pull requests in the typing repository on GitHub with the label 'topic: feature' that were opened or updated last week, excluding closed issues. --------------------------------------------------- The following issues and pull requests were opened last week: #1323 Allow `NotRequired[]` to be passed as a `TypeVar` opened by @not-my-profile https://github.com/python/typing/issues/1323 --------------------------------------------------- The following issues and pull requests were updated last week: #1043 TypingError: type checker will emit error with a message specified in typing stubs opened by @Akuli https://github.com/python/typing/issues/1043 #1319 Type hinting a non-iterator (non-consumable) iterable opened by @GideonBear https://github.com/python/typing/issues/1319 #1321 Typing decorators which enrich a class opened by @lijok https://github.com/python/typing/issues/1321 --------------------------------------------------- All issues and pull requests with the label 'topic: feature' can be viewed under the following URL: https://github.com/python/typing/issues?q=label%3A%22topic%3A+feature%22

1 0