[Python-Dev] Define a place for code review in Python workflow

R. David Murray rdmurray at bitdance.com
Tue Jul 27 14:05:40 CEST 2010


On Tue, 27 Jul 2010 13:11:48 +0200, Georg Brandl <g.brandl at gmx.net> wrote:
> Am 27.07.2010 10:54, schrieb David:
> >     I'd welcome any patch submitted to Rietveld for review.  However, your
> >     proposed "review.py" module does not exist as far as I know, and unless
> >     someone writes it, it won't.
> > 
> > Haven't personally tested that it works with Rietveld due to lack of patches
> > sitting around, but cursory investigation suggests that reports of non-existence
> > may have been exaggerated ;)
> > 
> > http://pypi.python.org/pypi/review/r537
> 
> Ah!  Well, a link to this instead of tirades would have been helpful from
> the OP; now at least we know what he's talking about.

Indeed.  If Anatoly had said, "Hey, there's this cool tool called
'review.py' on PyPI, and I think it would improve the tracker workflow
if it was used something like this....what do other people think?"

*That* kind of post would have gotten a completely different, and most
likely more constructive, response.

Anatoly, you might want to think about the fact that at this point I
suspect most people's reactions to anything you post tend to be along
the lines of "oh, another Anatoly rant" and either ignore it or look
immediately for what's *wrong* with what you post, instead of seeing
the good suggestions that are occasionally hidden inside your rants.
In other words, your negative attitude toward us results in us taking
a negative attitude toward you.  If you engaged positively with the
community instead of negatively, you'd have a much better chance of your
ideas getting a positive reception.

As an author I respect a lot once said, politeness is the grease that
keeps the gears of society working smoothly.  Your not "wasting time"
being a "polite bastard" is the equivalent of deliberately throwing sand
in the gears.  It is, to say the least, counter-productive to your stated
goals of improving the Python workflow for yourself and others.

--
R. David Murray                                      www.bitdance.com


More information about the Python-Dev mailing list