The full changelog for this release is here https://docs.python.org/release/3.11.7/whatsnew/changelog.html#python-3-11-7-final
Surprisingly not shown that obviously in the release announcements, but I guess that's fair since most of the changes will have no effect on 99.9999% of people.
Sounds fine, they're both immutable which helps.
UTF-8 is an encoding for unicode, that means it's a way of representing a unicode string as actual bytes on a computer.
It is variable length and works by using the first bits of each byte to indicate how many bytes are are needed to represent the current character.
Python also uses an encoding, as you describe in the article, but it's different to UTF-8. Unlike unicode, all characters in Python's representation of the unicode string use the same number of bytes, which is the maximum that any individual unicode character in the string needs.
I'd probably mess up a more detailed explanation of UTF-8 or Python's representation, so I'll let you look into how they work in more detail if you're interested.
The article says that CPython represents strings as UTF-8 encoded, which is not correct. The details about how it works are correct, just that's not UTF-8.
That's just a minor point though, nice article.
It's described in PEP 585, https://peps.python.org/pep-0585/#parameters-to-generics-are-available-at-runtime
At least the last season of scrubs was a different enough setting/cast, so even though it was definitely not as good, it didn't "ruin" it for me like some other series that have gone on too long.
Probably no time soon.
That video was the first thing I thought of :)
(https://youtu.be/YUpST_cQ1hM for anyone wondering)
Well I kept using it until Infinity died, which was only at the start of this month!
If I do decide to go back, it will be by compiling the infinity APK with my own API key, but I'm not feeling much of an urge to bother at the moment.
It'd be nice to have a rule specifically for the use of f-strings and template formatting in the same call, since that can easily be a security vulnerability.
I'm pretty sure most type checkers recognise both forms.
It probably really depends on the project, though I'd probably try and start with the tests that are easiest/nicest to write and those which will be most useful. Look for complex logic that is also quite self-contained.
That will probably help to convince others of the value of tests if they aren't onboard already.