Skip to content
This repository has been archived by the owner on Nov 21, 2022. It is now read-only.

Consider dropping the entire section on static checking (including 'sealed') #150

Open
gvanrossum opened this issue Aug 26, 2020 · 5 comments
Labels
accepted Discussion leading to a final decision to include in the PEP fully pepped Issues that have been fully documented in the PEP sc-feedback Issues raised in the steering committee feedback

Comments

@gvanrossum
Copy link
Owner

This section caused mostly confusion and bewilderment, and I don't consider it essential for the PEP. Static checkers have always managed to figure out how best to check existing Python constructs without formal specifications.

@gvanrossum gvanrossum added the sc-feedback Issues raised in the steering committee feedback label Aug 26, 2020
@Tobias-Kohn
Copy link
Collaborator

Agreed. Perhaps this is also something that might best be put into a separate PEP if we want to follow up on this.

@dmoisset
Copy link
Collaborator

+1

@willingc
Copy link

+1 to simplify and use a future PEP if desired.

@brandtbucher
Copy link
Collaborator

Agreed. I believe we just inherited it without modification from Ivan's first draft.

@gvanrossum gvanrossum added accepted Discussion leading to a final decision to include in the PEP fully pepped Issues that have been fully documented in the PEP labels Sep 16, 2020
@gvanrossum
Copy link
Owner Author

Done.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
accepted Discussion leading to a final decision to include in the PEP fully pepped Issues that have been fully documented in the PEP sc-feedback Issues raised in the steering committee feedback
Projects
None yet
Development

No branches or pull requests

5 participants