Huh?

Suuuuure, grocery store consolidation, and the consolidation of farming, and processed food has NOTHING to do with their ability to arbitrarily implement shrinkflation, with consumers having few or no other options. Also, kindly fuck off with the name-calling.

You're drawing the wrong conclusions.

Also, your writing is overflowing with emotion which is interpreted as idiological and not serious.

Reasonable people are not going to waste their time trying to have a civilized discussion with someone who drops f-bombs and isn't serious.

Edit: I wrote the above before looking at the rest of your comments. After looking at the rest of your comments, I rest my case.

And you wrote 4 condescending sentences and still haven't engaged with my point, at all. Next time just write "umadbro" like the troll you are, instead of pretending like you're anything else.

> your writing is overflowing with emotion which is interpreted as idiological and not serious.

no you!!!11. Man, just the absolute cringiest, most embarrassing way of engaging online. You spelled ideological wrong, too.

> I wrote the above before looking at the rest of your comments. After looking at the rest of your comments, I rest my case.

well hot fucking dog, I'm sure embarrassed now! What a joke. Guys, he rested his case!! I'm so owned and devastated!

You continue to prove my point...

...

I rest my case.

(Also, I'm sorry about the mispeling earlier.)

The premise of the article is wrong. Async in Python is popular. I'd expect most new web backends to use it.

The article says SQLalchemy added async support in 2023 but actually it was 2020.

Honestly I have no idea what people get out of trolling like this

are you talking about me?

I lived there, I took the path in the summer because it's super hot and humid in the summer. The winters were mild and not snowy at all.

Uh Toronto has had very mixed winters.

I live in northern Michigan. 25 F / -4 C is of course "cold", but it's not particularly problematic, you can under dress and it will be a fairly long time before you have problems. Down around 10 F / -12 C, you have to be a lot more aware.

And then if the regional/municipal governments have the equipment for it, a foot or two of snow a month really doesn't impact travel all that much (maybe for a few hours if there is a big storm).

I lived downtown by the path. I'd be surprised if there was a foot of snow total in the years that I lived there.

ok. The comment was about Toronto in general rather than just downtown.

Snowfall near the lake can be lower because of the mediated temperature. (Unlike south of the lake like in Buffalo were you can get high lake-effect snow). In a dense core, you can have very different patterns of accumulation due to road and building layout.

Winters can be sporadic. Last year's was bad. Year before was light.

This is last year: https://www.theweathernetwork.com/en/news/weather/severe/his...

What years were you there? I don't see how less than 'foot of snow total' is possible.

edit: These are the yearly totals (if the site's stats are to be believed). https://toronto.weatherstats.ca/charts/snow-yearly.html

Eyeball average puts it at like 100cm+

Ok

Whoosh

What's the "eating" part though?

{:} should have been the empty dict, now there's no good solution

I agree that {:} would be a better empty expression for dicts, but that ship has already sailed. {/} looks like a good enough alternative

There is a way to make it work. Python has no problem breaking things across major versions.

Python needed a breaking change for Unicode and a breaking change for exceptions and took it ages ago for a better future today - and it's still remembered as a huge PITA by everyone. I think you'll find everyone in the Python community disagreeing with you about a not-backwards-compatible Python 4.

If Python actually incremented the major version every time they broke backwards compatibility, we'd be on something like Python 36 by now.

Almost every version they break existing code. This is why it's common for apps written in Python to depend on specific Python versions instead of just "anything above 3.x".

Every minor release of Python is a breaking change. They deprecate stuff all the time, and remember the stdlib and the wider ecosystem has to also move in concert so the breaking changes cascade.

By major version I meant minor version, 3.13 -> 3.14 is a minor version in Python, but a major source of breaking changes, that is what I meant. There will be no Python 4

Are you suggesting to bump to Python 4 in order to be able to write `{}` instead of `set()` (or `{/}`) and simultaneously break all existing code using `{}` for dicts?

Breaking {} to be an empty set would be a HUGE breaking change, a _lot_ of code is already written where it is expected to be an empty dict. I don't think anyone in the Python committee would agree with breaking that

Jesus can you imagine if they announced Python 4? :-D

Double indentation

So? Other languages with pattern match similarly have such double indentation. C-style switch with unintended cases is weird.

What's DHH?

404