Re: Python does not play well with others

On 1/24/07, John Nagle <nagle@xxxxxxxxxxx> wrote:
Chris Mellon wrote:
> On 1/24/07, John Nagle <nagle@xxxxxxxxxxx> wrote:
>
>> Harry George wrote:
>> > John Nagle <nagle@xxxxxxxxxxx> writes:

> Just to be clear: The problem here is "my personal itch is not being
> scratched by other people for me", not "Python doesn't play well with
> others". You are not any more important than anyone else and assuming
> that anyone cares about your problems is a major fallacy. You have a
> specific library that doesn't meet your needs, and that you are not
> interested in maintaining yourself, so you are attempting to leverage
> some sort of community guilt trip to get other people to do it for
> you. That's dishonest and off-putting.

No, the problem is that these things are broken.


That's *your* problem. I don't write any code that uses SSL and so
it's not *my* problem. In a community effort, you either need to fix
your own problems or convince other people that they should fix them.
Saying "hey guys, this is broken" is a start. "You guys are shirking
your responsibilities and not supporting me the way I want to be
supported" is not, because it assumes an entitlement that you do not
have.

Python is the only major open source project I've encountered where
there's so much hostility to bug reports.


You've never submitted a duplicate bug to Gnome, have you? Regardless,
I see very little hostility toward bug reports. You confuse people
failing to satisfy your needs with hostility.

For a while, I tried submitting long, detailed bug reports showing
where in the C code a problem lies, and pointing out ways to fix it.
But I don't want to take over maintenance on the SSL package;
it's too delicate.

And yet, you are perfectly willing to claim that everyone else who
makes the same decision is failing, somehow. Could one not point out
that you are failing your responsibility to the Python community,
following the same logic?
.

Relevant Pages

  • Re: Interesting APAR OA27291 an undocumented change to GETMAIN Behavior in z/OS 1.10
    ... OA27291 is closed with some good information included in the APAR ... people understand that this APAR doesn't "fix" the failing ... For IBM-MAIN subscribe / signoff / archive access instructions, ...
    (bit.listserv.ibm-main)
  • Re: Tcl/Tk 8.5.3 RELEASED
    ... others fix the bugs they encounter. ... I was referring to the Tcl community, ... possibility to fix the bugs by anyone. ... Users of open source software are like the residents of my village in ...
    (comp.lang.tcl)
  • Re: Unresponsive Vendor
    ... The security community is there to make the world a better place. ... Let them fix it in their ... the vulnerability exists. ...
    (Security-Basics)
  • Re: Purveyor CGI mailbox capacity [bit long winded]
    ... this issue but thought I might poll the community ... no one is cursing the app, they are asking for a fix ... ... It's the underlying server platform corrupting the IPC between application and client. ... I was asking the Purveyor community, as represented by the subset that might happen to lurk in or about c.o.v., if anyone knew of a work-around to fix this aberrant Purveyor behaviour. ...
    (comp.os.vms)
  • Re: Licences
    ... Ludovic> community", provided enough people spend a little time to ... fix a couple of bugs that are particularly ... Ludovic> including AdaCore, who eventually will receive the fixes. ... make your fix available under the GMGPL instead of the GPL? ...
    (comp.lang.ada)