How else are you going to open your files in nano to do the programming on the prod server?

Plus it has markers for variable types just like Esperanto has suffixes for parts of speech. Wall was a linguist, after all.

Esperanto always struck me as more perl-like with each part of speech having its own suffix like perl has $ for scalars, @ for arrays, and % for hashes. Though perl is probably more like a bunch of pidgins…

Production errors.

LGTM (lunatic gunner targeting me)

You want an award? I hate working with JSON without a prettier.

A few weeks? How do you stay employed? How do you even feed yourself at that pace? Blocked on making a sandwich, I’ve got the wrong type of bread.

It’s three lines in an editor config file to standardize the indents across any editor: https://editorconfig.org/

In vscode, adding two extensions is all I need:, yamllint (if you don’t use linters, I don’t know how you do your job in any language) and rainbow indents. Atom had similar ones. I’m sure all IDEs are capable of these things. If you work at a place that forces you to use a specific editor and limits the way you can use it, that’s not YAML’s fault.

At a certain point, it’s your deficiencies that make a language difficult, not the language’s. Don’t blame your hammer when you haven’t heated the iron.

So it’s easy to enforce locally but you don’t have to. And it’s easy to see indentation on modern IDEs and you can even make your indents rainbows and collapse structures to make it easier to see what’s going on, but I guess since some people want to write it in vi without ALE or a barebones text editor, it’s bad? Like there are legit reasons it’s bad, and other people have mentioned them throughout the thread, but this seems like a pretty easy thing to deal with. I work with ansible a bunch and YAML rarely is where my problem is.

YAML mixes 2 and 4 spaces

I think that’s a user thing and it doesn’t happen if you have a linter enforce 2 or 4.

Your bedroom and your code sound dirty. No dessert until there are no more dirty clothes on the floor and all your merge conflicts are resolved.

I, too, got a Mohawk after the last outage.

These are all factors that let me say, with confidence, that there really aren’t any bugs in this this pull request.

That kind of thinking from Kent sounds like act one of a Greek tragedy.

woke

There it is. Thanks for finally being explicit about the kind of person you are. People like you are the reason cocs have to be made in the first place. Don’t bother responding, I’ll be blocking you.

Right, it’s not a company, and it relies on the unpaid labor of volunteers, who Peters was driving away. That’s mentioned in the thread. Though they are not a company with employees, they are still a community that needs to attract talent. You seem to be giving a lot more leeway to interpretations of Peters’ words than my comparison. Odd.

So he’s dismissing the training; in doing so he’s also dismissing that it’s worthwhile to try and have an environment free from sexual harassment. That’s not somebody I’d want as a representative of an inclusive community. The steering committee seems to agree.

From the Coc:

• Showing empathy towards other community members. We’re attentive in our communications, whether in person or online, and we’re tactful when approaching differing views.
• Being considerate. Members of the community are considerate of their peers – other Python users.
• Being respectful. We’re respectful of others, their positions, their skills, their commitments, and their efforts.
• Gracefully accepting constructive criticism. When we disagree, we are courteous in raising our issues.
• Using welcoming and inclusive language. We’re accepting of all who wish to take part in our activities, fostering an environment where anyone can participate and everyone can make a difference.

Yes. If you pulled that at your job, you’d be fired. He got suspended because he refused to accept feedback, he kept pushing and showing he had no intention to change his problematic behavior. Some people don’t get it until there are consequences to them.

This isn’t a court. That is how it worked.

Referring to multiple people, Tim being a big part of those people. So it’s primarily about Peters. You put it right there. Claiming it’s not just about him in pedantics and weak af.

I can’t tell if you picked up on my meaning when I mentioned the author’s fault. If you didn’t, maybe you’re not great at interpretation.

From Peters in the thread:

Nobody talked about demographic markers because they didn’t matter to anyone.

That reads to me that things were better before inclusive language was around.

I think this also is a good response to a different point to made about being rational:

Complaining about what it’s called isn’t what a person taking it seriously would do. It’s disruptive or subversive at best. With the general picture of his behavior from the suspension and his responses in the thread, I’m disinclined to believe his comments were merely said in a disarming manner.

In the same comment from Smith:

I want to assure everyone that the points we made in the original post were so pointed exactly because of the complaints we received from community members.

The “points” being three of the items that appeared on the suspension. This is specifically about Tim Peters.

So to sum up: they received complaints specifically about Peters. Then said people (plural) complain and that’s how they hear about it. If that’s not clear, it’s not the author’s fault.