Cheryl Sabella 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
___
Python tracker
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?
Éric Araujo mer...@netwok.org added the comment:
The “Documentation” component is used for bugs found in files under the Doc
directory of a CPython checkout or source tarball. PEPs are tracked in their
own repository and are not part of the CPython distribution. They are not part
of the
R. David Murray rdmur...@bitdance.com 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:
Alan Isaac alan.is...@gmail.com added the comment:
Bear with my confusion about your response. Are you saying that CPython
documentation bugs cannot be submitted here, or that this does not constitute a
CPython documentation bug? I assume the latter. But then, can you tell me
where to find
Éric Araujo mer...@netwok.org added the comment:
This tracker is for reporting bugs found in the CPython distribution, not PEPs,
PyPI or other websites. You can write to the python-dev mailing list if the
XXX bother you.
--
assignee: docs@python -
components: -Documentation
nosy:
New submission from Alan Isaac alan.is...@gmail.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