[Python-Dev] PEP process entry point and ill fated initiatives (original) (raw)
Guido van Rossum guido at python.org
Thu Nov 28 19:39:57 CET 2013
- Previous message: [Python-Dev] PEP process entry point and ill fated initiatives
- Next message: [Python-Dev] PEP process entry point and ill fated initiatives
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Anatoly, the Python community is a lot more diverse than you think. "Pull requests" (whatever that means) are not the way to start a PEP. You should start by focusing on the contents, and the mechanics of editing it and getting it formatted properly are secondary. The process is explained in PEP one. Your bug report would have gotten a much better response if you had simply asked "what is the process, I can't figure it out from the repo's README" rather that (again) complaining that the core developers don't care. Offending people is not the way to get them to help you.
On Thu, Nov 28, 2013 at 9:45 AM, anatoly techtonik <techtonik at gmail.com>wrote:
I wanted to help people who are trying to find out more about PEP submission process by providing relevant info (or a pointer) in README.rst that is located at the root of PEPs repository. You can see it here.
https://bitbucket.org/rirror/peps I filled this issue with b.p.o http://bugs.python.org/issue19822 However, as you may see, I met some resistance, which said me to discuss the matter here. So, I'd like to discuss two things: 1. is my README.rst enhancement request is wrong? 2. what makes people close tickets without providing arguments, but using stuff like "should"? It is not the first stuff that I personally find discouraging, which may be attributed to my reputation, but what's the point in doing this? The only logical explanation I find for resistance in this particular case is that people in core Python development don't take usability and user experience matters seriously. Most of core development is about systems, not about people, so everybody is scratching own itches. I wish that usability and UX was given at least some coverage in Python development regulations. -- anatoly t.
Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%40python.org
-- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20131128/5f18349d/attachment.html>
- Previous message: [Python-Dev] PEP process entry point and ill fated initiatives
- Next message: [Python-Dev] PEP process entry point and ill fated initiatives
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]