You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2019-01-05.17:41:12.508>created_at=<Date2019-01-03.17:34:26.578>labels= ['docs']
title='PEP 257 (active) references PEP 258 (rejected) as if it were active'updated_at=<Date2019-02-21.23:32:21.273>user='https://github.com/ExplodingCabbage'
Please see PEP-258, "Docutils Design Specification" [2], for a detailed description of attribute and additional docstrings.
But PEP-258 is rejected. It doesn't seem coherent that an active PEP can defer some of its details to a rejected PEP - and indeed it makes me unsure how much of the surrounding commentary in PEP-257 to treat as active. e.g. should I treat the entire concepts of "attribute docstrings" and "additional docstrings" as rejected, given the rejection of PEP-258, or are they still part of the current spec, given that they're referenced in PEP-257 prior to any mention of PEP-258? It's currently completely unclear.
A rejected PEP still exists in perpetuity, and can still be used as a reference. Also, the reason for PEP-258's rejection is not that it is invalid, but that it's not slated for stdlib inclusion. So I think that the reference is still useful, and I don't think there's anything that needs to be done here.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: