[issue19822] PEP process entrypoint

anatoly techtonik report at bugs.python.org
Thu Nov 28 18:19:30 CET 2013


anatoly techtonik added the comment:

> The ticket has been closed by two people. Why do you keep re-opening the ticket?

Because you're not providing any arguments. If it is not important for you, just ignore. If something is not clear - ask. What you do is just closing the stuff, because you _feel_ that is not an issue. Provide rationale, address my points and then I'll close it myself. The particular stuff that is not clarified:

>> Post the link to correct process into README.rst and then this
>> issue can be closed.
> The repo readme is not the right place for this. Christian already
> mentioned the PEPs and anything should go into the dev guide.

I want to know why PEPs repository README is not the place to direct users to starting point for submitting enhancement proposals?

> If you have something to contribute, please open a ticket, add a patch
and request review.

I am already keep opening it, damn. I want to contribute an improvement for the PEP process and not forget about it. That's why I fill in into tracker, and not into email.

----------
resolution: invalid -> postponed
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19822>
_______________________________________


More information about the Python-bugs-list mailing list