Do you feel bad because of the Python docs?
wuwei23 at gmail.com
Thu Feb 28 05:18:46 CET 2013
On Feb 28, 12:05 pm, Rick Johnson <rantingrickjohn... at gmail.com>
> On Wednesday, February 27, 2013 5:25:25 PM UTC-6, alex23 wrote:
> > Ranting on public forums is nothing but posturing at best, and at
> > worst an attempt to blackmail-by-shame people into doing something for
> > you. Same goes for calls for "the community" to "fix" things.
> What you call ranting is most times people venting frustrations
> BECAUSE they want to help, but nobody is allowing them to be a
> contributing member of the community.
You claim that no one has time to write a bug report. I point out that
if they can spend the time ranting about the bug, then they have the
time. You then proceed to try and reframe the discussion to something
Venting frustrations isn't contributing. If someone is confused about
how to contribute, they could just *ask*, as people _regularly_ do
here, and are always given reasonable direction how to do so.
> When someone tries to offer help, in the form of constructive criticism, and then somebody snaps at them, they then loose the will to help. I myself would love to contribute my "quite awesome" re-write of the Tkinter GUI library, but due to the friction i've encountered on this list, i am resigned to keep it to myself (at least for the time being). Which is sad because python (and python programmers) could greatly benefit from a polished Tkinter.
Insisting your personal project is shoved into the standard library
isn't helping. Write a PEP. Put the code up on PyPI. There's a well-
established path for progressing code from "look what I done make!"
into something that is considered part of Python.
> Alex i can assure you, there DOES exist a very harsh attitude to outside opinions within this community.
Don't extend this list's reaction to you and your particular blend of
idiocy to the general response to opinions.
> Case in point: Why should ANYBODY need to voice Python problems on various blogs around the web?
The two main reasons seem to be: vanity, and an unwillingness to
listen to criticism.
> This is why i will AGAIN mention my PyWarts list (Hypothetical at this point).
"Hypothetical" sums up pretty much all of your supposed contributions
> We need an official place for the many problems of Python to be discussed in a fair and open manner. A place that will be open to noobs and frequented by pythonisitas (including the BDFL himself!)
Starting a new forum just fragments the discussion even further.
> Path of a Python Issue
> 1. All perceived problems with python get voiced on the PyWarts list
> 2. After considerable discussion, and if we can widdle the problem down to a tangible bug, then a bug gets opened on the tracker.
> 3. Hopefully the bug will be resolved and closed ASAP.
Ah, so it's your way or no way, yet again.
THERE ALREADY EXISTS A PATH FOR DEALING WITH ISSUES.
> This is a linear path of inclusion that will prompt people to participate.
Right, until someone doesn't get the response they want and they
agitate for this to happen on Stackoverflow, or IRC, or their brand
new forum they've set up. You're not the first person to want to
impose your own brand of tyranny on the process.
> You and i both know we need more people working at the tracker
No one is going to be "working at the tracker", because no one is
*paid* to do such "work". People can participate by contributing, or
they can choose not to. The latter should also STFU if they're not
willing to contribute, but this seems to be a position you're unable
or unwilling to understand.
> Neither this community nor this language can survive without a steady adoption of new members.
The current process is not doing anything like the damage to the
uptake of Python that you constantly claim it is, but you do love your
More information about the Python-list