New submission from Alan Isaac email@example.com:
In PEP 227 missing text is marked with XXX. Most of this is just calls for examples and elaboration. However under the Implementation section XXX marks a substantive question about the documentation.
Fixing this may be low priority, but a tracker search suggested it is currently not even being tracked ...
---------- assignee: docs@python components: Documentation messages: 127184 nosy: aisaac, docs@python priority: normal severity: normal status: open title: pep 227 missing text type: feature request
R. David Murray firstname.lastname@example.org added the comment:
Eric, what you say is technically true, but we don't have any other place to track PEP bugs.
---------- assignee: -> docs@python components: +Documentation nosy: +docs@python, r.david.murray resolution: invalid -> stage: committed/rejected -> needs patch status: closed -> open type: -> behavior
Mark Lawrence added the comment:
PEP 227 (Not 277 as wrongly quoted in one place) is about Statically Nested Scopes. There are several XXX place holders in the current doc. For all I know it would be possible to simply remove all of them, but who is best placed to give a definitive answer?
---------- nosy: +BreamoreBoy
Cheryl Sabella email@example.com added the comment:
Moved to the PEP issue tracker. https://github.com/python/peps/issues/557
---------- nosy: +csabella resolution: -> later stage: needs patch -> resolved status: open -> closed