A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2015-July/140845.html below:

[Python-Dev] How do we tell if we're helping or hindering the core development process? (was Re: How far to go with user-friendliness)

[Python-Dev] How do we tell if we're helping or hindering the core development process? (was Re: How far to go with user-friendliness) [Python-Dev] How do we tell if we're helping or hindering the core development process? (was Re: How far to go with user-friendliness)Baptiste Carvello devel at baptiste-carvello.net
Tue Jul 21 11:27:56 CEST 2015
Hello,

since this thread is restarting in debriefing mode: one thing struck me
as a non-committer following python-dev.

It seems that we (non-committers) have a difficulty making the
distinction between pre-implementation design discussions (PEPs beeing
the typical example), where relevant technical comments are welcome,
even on minor points, and post-commit discussions, where the maintainer
already made the design decisions, and discussing anything except real
bugs is unhelpful.

In this particular thread, the distinction was all the more blurred by
the very generic title. A thread titled something like "Commit-xxx:
should mock try to detect user typos?" would have been much less likely
to attract comments discussing principles in the abstract, without
taking the context into account.

Regards,

Baptiste

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4