On Tue, Aug 27, 2019 at 8:04 PM Stephen J. Turnbull <turnbull.stephen.fw@u.tsukuba.ac.jp> wrote:
Paul Moore writes:

 > [S]ubjecting a newcomer to the need to [deal with extra
 > requirements from other participants] right up front isn't exactly
 > fair or helpful.

But avoiding that is what core-mentorship is for.  Perhaps we can
advertise that list better, and maybe more people can mentor there.
 
I would like to add my fresh experience with the whole process and why it may seem different from here, compared to how you see from there.
I tried to go by the the official doc:

https://devguide.python.org/communication/#communication (direct quote):  

Python-ideas is a mailing list open to the public to discuss ideas on changing Python. If a new idea does not start here (or python-list, discussed below), it will get redirected here.
Sometimes people post new ideas to python-list to gather community opinion before heading to python-ideas. The list is also sometimes known as comp.lang.python, the name of the newsgroup it mirrors (it is also known by the abbreviation c.l.py).

Which I read as "you may post in python-list, but it will eventually get redirected here".
Concerning the core-mentorship from what I read about it (and in it) it did not look as a place to discuss new ideas to me, but the place where new contributors are looking for help when (starting) contributing.

>But a proposal that comes to Python-Ideas is going to be presumed the
>object of public discussion for the benefit of Python  

I guess more emphasis (or clearer formulation) could be used in the doc, to explicitly direct people to one place (which I presume should be python-list from what you wrote) and to explain the "process of acceptance" into python-ideas.

In retrospect maybe posting in python-list first would give me some ideas and better understanding on what is used (and expected) by others, but I had to post here first to realize it.
 
Richard