Live data from Hacker News

A post by Guido van Rossum removed for violating Python community guidelines

discuss.python.org

281–289 of 289 posts

Re: A post by Guido van Rossum removed for violating Python community guidelines

#281
post #279

It's wonderful seeing this three days later after Guido himself has come in to say that this was nothing nefarious and more of an automation mishap. Yet here stands dozens of comments from people crying about how code of conduct is ruining the world and the PSF and SC should be dismantled. As is often the case, there is usually more to the story and we would be better off learning what really happened instead of imme…

This is not one event in isolation, but rather a string of similar ones. And several folks did flag the post, did they not?

Re: A post by Guido van Rossum removed for violating Python community guidelines

#282

Earlier quoted context omitted.

Even so, why not use full range voting (0-100) instead? Wouldn't it extract more information?

An arguable disadvantage of full range voting is that it overweights people who vote binary 0/100 and underweights people who vote 80-100. Since the former is almost always strategically advantaged, it seems fairer to just cut out the middle.

this is a zero sum fallacy. social choice is not zero sum. voters who use intermediate scores donate more utility to society than they give up by not being strategically normalized, leading to an increase in net utility. with enough honest voters, even the "naive suckers" are better off than they would have been under a normalized approval-style ballot. https://www.rangevoting.org/ShExpRes

also see the "no math skills" argument.

https://www.rangevoting.org/RVstrat6

Re: A post by Guido van Rossum removed for violating Python community guidelines

#283

Earlier quoted context omitted.

The very simple fix is there is to auto-scale everyone's scores into weights (percentages that add to 100).

That's a horrible idea that reintroduces spoiler effects.

yep.

https://www.rangevoting.org/RVstrat6

Re: A post by Guido van Rossum removed for violating Python community guidelines

#286

Earlier quoted context omitted.

> The use of "master" in git has no historical or etymological ties to slavery whatsoever as outlined above. QED. Not the argument I, or anyone else, is making The use of "master" in Git may remind someone of slavery, which we don't want to do. For their sake. That's the argument actually being made and I think you'll notice it's much harder, if not impossible, to refute. That's the argument you need to target, not w…

>Not the argument I, or anyone else, is making That was the exact argument others were making. >The use of "master" in Git may remind someone of slavery, which we don't want to do. For their sake. The removal of "master" in git may remind others of fascism, which we don't want to do. For their sake. >That's the argument actually being made They'd be delusional and wrong because the etymology doesn't stem from slavery…

No response. Not surprised.

Re: A post by Guido van Rossum removed for violating Python community guidelines

#287

Earlier quoted context omitted.

> All three of those have declined. It's less readable than it used to be, it's definitely more complicated (not just complex, complicated), and the standard library is declining rapidly in relevance as it ages. I find it much more readable, and more importantly more expressive . Certain new features are missteps IMO, but I just don't use them. But more importantly, the language has been moving away from cryptic %-en…

The walrus operator is nice, except in comprehensions. f-strings are great, except for the `=` debugging operator. Dictionary merging and update operators contradict the "one way to do it" with weird and confusing syntax that's completely redundant to methods that already exist. Type hints are a sore spot for me. They're good enough when you just don't remember whether an argument is an object or a string, for exampl…

> f-strings are great, except for the `=` debugging operator

What's wrong with `=` debugging operator in f-strings?

Re: A post by Guido van Rossum removed for violating Python community guidelines

#288

Earlier quoted context omitted.

You are making a general point, but does it apply specifically? Here's the Python Code of Conduct for communication on official Python forums, and comm+behavior at official Python events: https://policies.python.org/python.org/code-of-conduct What specific items do you disagree with? * The top section "Our Community" is just general stuff like "be respectful." Is that a problem? * The list of "Inappropriate Behavior"…

I am challenging the very premise of a CoC. They are useless newspeak documents made only to enforce the ideology of those in positions of power and not benefit the project. “Don’t be an ass” is standard fare in polite society. Do you need to be told “don’t scream at people” every day when you leave the house? Perhaps those with low inhibition and self-control need such a reminder, but I would argue those are the one…

> Do you need to be told “don’t scream at people”

Not any more, now I've been told

I am one of those people who had to be told. Glad I was to.d why people were scared of me. It was very helpful

If you do not need it, good on you. Do not read it

Re: A post by Guido van Rossum removed for violating Python community guidelines

#289

Earlier quoted context omitted.

[flagged]

> could just as easily use your exact argument to say Audio got it from slavery. Which is what I'm doing. You're welcome to say this, but it has no basis in fact.

No response from him. BTFO.
Post reply on HN