I was there when Chad launched Testosterone back at PyCon 2006. Good times, indeed. I don't think naming a test app "Testosterone" is particularly sexist, espe

I was there when Chad launched Testosterone back at PyCon 2006. Good times, indeed. I don't think naming a test app "Testosterone" is particularly sexist, especially next to a lot of what we've seen happening recently, but I think he's making the right decision by renaming it and publicly acknowledging the issue. Sexism is a continuum. This clearly isn't as egregious as the "CouchDB + Ruby: Perform Like a Pr0n Star." talk at gogaruco or last weeks' Geeklist kerfuffle, but we need to recognize that there is a pervasive boys club atmosphere in much of the programming world. Testosterone and projects/attitudes like it set up this association of "doing X, which is tricky and requires great knowledge or skill from the programmer" is "manly" and "manly" is a positive thing. OK, Testosterone also makes a play on using curses as being manly, which is clever, but this is certainly a pervasive attitude (I remember Linus Torvalds famously making a statement to the effect of "Debugging with printk puts hair on your chest" as justification for not including debugging facilities in the Linux kernel). This kind of language is common and many of us (even women) are guilty of using it in varying degrees. Individually, these aren't a big deal. But the overall atmosphere is off-putting to many and we need to at least be aware of that. I applaud Chad for responding in a professional and respectful manner. We need more of this and less of the "I'm sorry you found that offensive" non-apology apology attitude that's been the typical response. This should be the template for the tone of future discussions. That said, "assertEquals"? Really? camelCase for a Python library? :(