Skip to content

Conversation

@ilevkivskyi
Copy link
Member

This includes couple edits inspired by recent discussions:

  • Remove mention of metaclasses from implementation details section (PEP 560 makes them unnecessary).
  • Explcitly mention callback protocols as an important use case.

cc @ambv @JukkaL @gvanrossum

Copy link
Member

@gvanrossum gvanrossum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are callback protocols well known to the other type checker teams, or do we have to remind them of this addition to the PEP?

Co-Authored-By: Jelle Zijlstra <jelle.zijlstra@gmail.com>
@gvanrossum gvanrossum merged commit 74f0fb2 into python:master May 24, 2019
@gvanrossum gvanrossum deleted the update-544-f branch May 24, 2019 05:16
@ilevkivskyi
Copy link
Member Author

Are callback protocols well known to the other type checker teams, or do we have to remind them of this addition to the PEP?

I am not sure, but it is a relatively old feature in mypy (since August IIRC) and it appeared many times in discussions on Gitter. Plus IMO it is not that special from the point of view of "theory", it is just important from practical point of view.

@ilevkivskyi
Copy link
Member Author

On the other hand we can post a brief summary of all recent changes to the PEP. What do you think?

@gvanrossum
Copy link
Member

gvanrossum commented May 24, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants