Planning Session

Notes: https://docs.google.com/document/d/1PIOvLZyep1qVqTq5P3wcI6TNe5UkKbR52qHjSZ1EuDU/edit

Issues

NamedTuple, TypedDict and Generated Types

• Agreed on preferring class-based syntax for NamedTuple and TypedDict
• What code generation decorators should be supported? (dataclass?)

Integrate PEP 570

• mypy may not support PEP 570 when run under < Python 3.8, but the draft PEP says that stubs can start to use new features as soon as a version is released.

Monty Pythonify the PEP

Tuple-based Version Checks

Typeshed section

__all__?

• Should __all__ be supported in stubs to avoid exposing private definitions?

How to treat errors in stub

• Should we recommend to never report errors in/for conforming third party stubs?

PRs

Integrate PEP 570.

• Blocked on https://github.com/srittau/type-stub-pep/issues/35

Start the 'Supported Constructs' section

[WIP] Add Version and Platform Checks section

Unfinished content

Supported Constructs > Enums

Supported Constructs > NamedTuple

Supported Constructs > TypeVar

Supported Constructs > NewType

Supported Constructs > __getattr__, __setattr__

• Also mentioned in Content section

Supported Constructs > Module-level __getattr__

• Also mentioned in Content section

Supported Constructs > Is __all__ meaningful in a stub? What does it do?

• Discussed in https://github.com/srittau/type-stub-pep/issues/20

Supported Constructs > Forward references don't need quotes or a __future__ import

• Also mentioned in Style section

Supported Constructs > How to treat definitions with a leading underscore?

Supported Constructs > Callback protocols

Supported Constructs > Module-level asserts

Release Planning

1. Finish Writing
2. Editorial Pass
3. Find a sponsor?
4. Submit as PEP
5. Post publically (typing-sig? python-dev?)