I have no idea what you’re talking about. Typer adds a nice type annotation based interface which is both nice to use and means all your arguments are statically typed checked.
I don’t use async Python normally (IMO it’s one of those “if you need this you shouldn’t be using Python” features).
Typer and Pydantic are absolutely mandatory on any Python project I write. A million times better than argparse and dicts everywhere.
Sure but that’s orthogonal to f-strings.
To be fair this was quite wtf-free. Mostly just unimportant formatting subtleties and stuff you’d never write.
Python definitely has bigger WTFs, like bool being an int, implicit bool conversion, implicit iteration of strings, etc.
i just said it’s supposed to be used as a high-level glue to hold low-level things together.
Exactly. You essentially said it’s ok for Python to be slow because it’s supposed to only be used to tie together things written in fast languages. That’s utter bullshit. It was never designed with that intent, it’s just that it turns out people do use it like that because it’s so slow.
It’s frustrating when people make excuses for problems - even saying that there isn’t a problem. Like, if everyone was saying “I like Python even though it is extraordinarily slow and will never be fast, which is a shame”… That’s fine. Saying “Python isn’t supposed to be fast and you shouldn’t want that” is delusional.
It’s not just Python where this phenomenon happens - I gave the example of Git (“you shouldn’t want to version control binaries so the fact that Git sucks at it isn’t really a problem at all!”). Another common one is distributing binaries on Linux - you shouldn’t want to do that so it doesn’t matter that it’s a pain in the bum.
Pet peeve I guess.
they’re built that way because python is a flexible way to glue functionality together
Lol no. They’re built that way because it’s fast! Can you imagine how slow Python would be if it was self hosted? Actually I bet someone has tried that…
Yep - go and benchmark that and get back to me in a few days when it’s finished running hello world, lol.
just like how with git, we have lfs
Have you ever actually used LFS? It’s a pretty terrible experience.
Nonsense. You are only “supposed” to do that because if you are using Python and you want performance you have no other choice!
Reminds me of people saying you aren’t “supposed” to store binaries in git - yeah only because git is so bad at it! When we were all using SVN people would have said “you aren’t supposed to have multiple people editing the same file simultaneously” as if it were a fundamental truth.
And Python isn’t “a glue language”. It’s often used like that but there are many many pure Python projects.
Nonsense. You are only “supposed” to do that because if you are using Python and you want performance you have no other choice!
Reminds me of people saying you aren’t “supposed” to store binaries in git - yeah only because git is so bad at it! When we were all using SVN people would have said “you aren’t supposed to have multiple people editing the same file simultaneously” as if it were a fundamental truth.
And Python isn’t “a glue language”. It’s often used like that but there are many many pure Python projects.
You shouldn’t blindly trust those numbers. If you actually read the Python code a lot of them use ctypes to just delegate the work to C. It even says that at the bottom of the page.
Seems like they’ve finally started calling these out - search for “contentious” on this page:
https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/python3-go.html
Absolute rubbish. Go is typically something like 2-3x slower than “native” languages like C and Rust. Python is typically 50-100x times slower. Go is much much closed to C than it is to Python.
That ignores just how slow it is. It’s on the order of 100x slower than “fast” languages like Rust and Go, so doubling in speed… while nice for Python Devs doesn’t really make it fast on an absolute scale. They need to double it’s speed a few more times at least.
Ah yeah I agree. Misread your comment.
I disagree. You can write a lot of high quality Python code (yeah it exists) before you need to use inheritance. If you’re reaching for inheritance as the solution to all complexity, GoF-style, then you’re doing it wrong.
It’s an occasionally useful tool that has its place, not something you should instinctively reach for.
It’s good advice for JavaScript because JavaScript really fucked this up. But it’s a bit confused to say “don’t use functions as callbacks unless they were designed for it”.
The problem isn’t really even directly related to callbacks.
A better way to state it would be “don’t pass extra arguments to functions that don’t use use them”.
TL;DR, big-O ignores the constant factor. If you already know what that means you don’t need to read this…
Pretty good for a week and a half! I would recommend setting up a project using uv and also adding type hints and check them with Pyright (NOT Mypy).
Instead you should just use an autoformatter. Black is good. Ruff is probably good too but I don’t have a lot of experience with it. YAPF is not good; don’t use it.
I mean, nobody uses Python for execution speed precisely because it is so slow.
Are you… ok? I think maybe you should see a psychiatrist.