Hi folks, one of the list admins here, my eye was caught by this ongoing discussion.
I’m responding to this message out of several on this topic, because it brings up an interesting point - do we have good documents on this process that are attached to python-ideas and/or core mentoring lists? I did some googling about, and the most specific thing I found was this description of python-ideas: “”" This list is to contain discussion of speculative language ideas for Python for possible inclusion into the language. If an idea gains traction it can then be discussed and honed to the point of becoming a solid proposal to put to python-dev as appropriate. “”” which seems insufficient... Should we provide a more explicit or detailed rationale for python-ideas, based on this thread? We could make some or all of the following points — * python-ideas is for discussion of speculative ideas * the process is, (1) refine ideas here, (2) after broad acceptance of basic premise, develop an informal writeup, (3) find a core dev sponsor who will back turning this into a PEP * pointers to PEP 1, https://www.python.org/dev/peps/pep-0001/, and Python governance, https://www.python.org/dev/peps/pep-0013/ * pointers to core mentorship list, https://www.python.org/dev/core-mentorship/, and python developer documentation, https://devguide.python.org * pointers to this thread * please note that the burden for adding features to the language is high because you’re affecting so many people, increasing support burden, etc. etc. * note that everyone working on python is a volunteer, please respect their time and effort. I could try drafting something and passing it by people on this list to see what they think, but I’m wondering if I’m missing an obvious resource that I could just link to in the python-ideas description. best, —titus > On Jul 26, 2019, at 10:49 PM, Kyle Stanley <aeros...@gmail.com> wrote: > > Eric V. Smith wrote: >> In addition, I find it hard to believe someone couldn't find a sponsor >> for a well-written PEP. I'm happy to sponsor such a PEP, even if I think >> it will be rejected. Rejected PEPs serve a useful purpose, too, if only >> to point to when the same issue comes up in the future. > > Do most of the other core developers also share this perspective? Even > though PEPs were not intended to be intimidating, they definitely can be > for those who are less familiar with the process. I can imagine that many > people would think that a "sponsor" would mean fully convincing someone > to be completely on board with their idea. > > As someone who only more recently began contributing to Python, my previous > perception of PEPs were these monolithic technical > documents that were well approved by the entire community. I'm slowly > starting to see them more as simply being well structured proposals after > having seen more of them. > > To many outside of the development community though, such as those proposing > ideas, their impression of a PEP is probably based on the > massive ones such as PEP 8. Although it was purely comical, I think PEP 401 > helped me quite a lot to see them as less intimidating. PEP 581 is a good > example of an actual approved one that's easily digestible. > _______________________________________________ > Python-ideas mailing list -- python-ideas@python.org > To unsubscribe send an email to python-ideas-le...@python.org > https://mail.python.org/mailman3/lists/python-ideas.python.org/ > Message archived at > https://mail.python.org/archives/list/python-ideas@python.org/message/4WVJMMCFKQOUBSO452K45KIARIJ2Y6KB/ > Code of Conduct: http://python.org/psf/codeofconduct/ _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/DJV477F6MCFK34A2L7YPJHLCJTB533XD/ Code of Conduct: http://python.org/psf/codeofconduct/
