Those new error messages look divine compared to what we've had up until now! They seem like they might have been inspired by Rust's error message format to me, but I'm not sure. I'm just happy that I won't have to split chained operations onto individual lines anymore just to have any ability to debug them with the regular old stacktrace errors.

Nice to finally have TOML support in the stdlib, especially considering pip's dependence on it.

"What’s New In Python 3.11" https://docs.python.org/3.11/whatsnew/3.11.html

There’s a nice article with some code examples here of the new features: https://realpython.com/python311-new-features

Now if only Azure Functions would support Python versions newer than 3.9!

Come on Microsoft!

Same on AWS iirc, why would they? the speed up will loose them money, whoever implements that is not getting a promotion to L7!

Shoot, Lambda only goes up to 3.8. I miss the decent error messages.

AWS supports up to Python 3.9 right now: https://aws.amazon.com/about-aws/whats-new/2021/08/aws-lambd...

Here's a public comment from the Azure Functions team about when they expect 3.10: https://github.com/Azure/azure-functions-python-worker/issue...

(They're hoping for 3.11 support to be available not long after, thanks to a better release system coming soon)

> and it will experience repulsive gravity that will push it back to the original region, but then it will experience the pull from the singularity again and will repeat this process forever.

If the observer had a charge, wouldn't this create radio waves, bleeding off energy?

Hasn't radiation from black holes been observed? It's called Hawking radiation I think.

I've been really looking forward to the variadic generics. ML and data code is full of types like "FloatTensor" and "DataFrame" which really don't narrow things down. Hopefully this will make its way into the ecosystem asap.

I sure do hope Arbitrary Literal String Type (https://peps.python.org/pep-0675/) solves the problem they think it does and doesn't drive every typechecker in the world stark-raving mad

    literal_name: LiteralString
    expect_literal_string(f"hello {literal_name}")
    # OK because it is composed from literal strings.

Maybe I'm being too cynical and this is laying the groundwork for py4000 where they will type check at runtime

This release sent me down a rabbit hole (it started with the sidenote on physics), which made me wonder what software https://discuss.python.org is running on. I couldn't find a link to GitHub or elsewhere or any project page which could enable me to host such a discussion board on a server. Does it have a name?

I'm fairly sure it's Discourse[1]. They switched to it quite recently.

[1] https://www.discourse.org

From the HTML source code:

    <meta name="generator" content="Discourse 2.9.0.beta10 - https://github.com/discourse/discourse version 0ffd40867466b0f6b6fbcbc08e01d1a62633d915">

For anyone who finds this thread later, it seems that https://news.ycombinator.com/item?id=33327896 overtook it (216 comments as of right now)

I was looking forward this release. The performance improvements in this release are insane! I just created a ticket for my team to upgrade all our production Pythons to this release.

I am curious what kind of work are you guys doing that you need a sudden upgrade? Some DS/ML Work?

This is for http://www.OnlineTools.com where we do all kinds of image and data conversions.

Brave going onto a .0 release ;)

Engineers just postponed the upgrade because of this very reason. I agree. We’ll wait for .1 or .2.

Looking forward to the 1.22x speedup! Been using Nim for a lot of those types of use cases personally.

I thought not all features were available in 3.10 yet

I believe you may be thinking about a different language? Python only releases a feature release yearly. Features which don’t make it into a release like 3.9, 3.10, and 3.11 are usually agreed upon before the feature freeze window to avoid specifically this.