I'm quite active in the CoffeeScript community, but am also on a ton of medication that ultimately means I won't implement much of what I suggest doing, but the core devs understand the situation well enough to respond accordingly.

It really does help when people know what they can reasonably expect from others, and it doesn't take much to let them know. None of this has ever prevented me from being involved. It just prevents me from wasting other people's time. -- Carl

On 23 June 2017 at 21:09, Paul Moore <p.f.moore@gmail.com> wrote:
On 23 June 2017 at 19:28, Brendan Barnwell <brenbarn@brenbarn.net> wrote:
> So to put it succinctly, as someone who's found discussion on this list
> interesting and valuable, I think there is value in having discussion about
> "what would Python be like if this idea were implemented" even if we never
> get very far with "how would we implement this idea in Python".  And I would
> find it unfortunate if discussion of the former were prematurely restricted
> by worries about the latter.

No-one is proposing otherwise, just that people are open when starting
a discussion as to whether they anticipate being able to follow
through with an implementation if the idea meets with approval, or if
they are simply making a suggestion that they hope someone else will
take up. That's not too much to ask, nor does it in any way stifle
reasonable discussion (it may discourage people who want to
*deliberately* give the impression that they will do the work, but
actually have no intention of doing so - but I hope there's no-one
like that here and if there were, I'm happy with discouraging them).

So I'm +1 on Brett's request.
Python-ideas mailing list
Code of Conduct: http://python.org/psf/codeofconduct/