- Qt “cute” (the UI framework)
- QT “cutie” (QuickTime the Apple media framework)
It doesn’t. read the first words behind the link you posted:
Page Status: Outdated
Here is the actual one: https://packaging.python.org/en/latest/tutorials/packaging-projects/
Uv and pip do the same thing, uv is just faster.
Hatch has the same role as Poetry or tox: managing environments for you.
Applications should be packaged properly, in a self contained installer for exactly this demographic. It’s not Python’s fault that this isn’t common practice.
Sure, there was some hyperbole. Some people need some specific setuptools plugin or something. Almost nobody.
It’s not a standard, it’s built on standards.
You can also use Poetry (which recently grew standard metadata support) or plain uv venv
if you want to do things manually but fast.
It’s fixed, and the python version had nothing to do with it. Just use hatch
No it’s not. E.g. nobody who starts a new project uses setup.py anymore
Because they just have their own brain chemistry as the basis of it whereas the above comment clearly states:
Rust has proven empirically that the tradeoff between performance and safety doesn’t need to exist.
Which is truth. And it’s much easier to base a coherent argument on truth rather than vibes.
Whoever dies first loses.
Wow you’re insane. “I know, I’ll discredit the woman who just pointed out that it’s hard to get credit in her field as a woman ”
Python is just glorified shell scripting
Absolutely not, python is an actual programming language with sane error handling and arbitrarily nestable data structures.
I don’t like the indentation crap
Don’t be so superficial. When learning something, go with the flow and try to work with the design choices, not against them.
Python simply writes a bit differently: you do e.g. more function definitions and list comprehensions.
Not only is there a UInt8Array, there’s also a bunch of others: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray#typedarray_objects
Great point, but this part of the quote is still dumb as rocks:
Coding is just kind of like the language that we talk to computers. It’s not necessarily the skill in and of itself. The skill in and of itself is like, how do I innovate? How do I go build something that’s interesting for my end users to use?
Sure, if you have a big workforce hand-coding UI, you might replace some of them by better tools. But things like that are a fraction of a fraction of the responsibilities developers have
Yeah, the motivation here is “please panic-buy our GPUs/please panic-buy into our cloud GPU infrastructure ”
Huh, I really like code like that. Having a multi-step process split up into sections like that is amazing to reason about actual dependencies of the individual sections. Granted, that only applies if the individual steps are kinda independently meaningful
To adapt your example to what I mean:
Baz do_stuff(int count, boolean cond) {
Foo part1 = function1(count);
Bar part2 = function2(cond);
return function3(part1, part2);
}
This allows you to immediately see that part1 and part2 are independently calculated, and what goes into calculating them.
There are several benefits, e.g.:
dbg!()
for Rust users
He works on Linux where he controls the whole stack down to the metal and I love that for him, but other people have to call library code, and them debug that if it doesn’t work as they thought it would.
Hatch is great. It’s easy to get started but I wouldn’t call it simple. Flit is simple, because it’s limited.
Hatch is complex enough to allow you to override everything, which makes it not simple, but also not complicated.
I agree, although it undersells hatch and has a title that made me roll my eyes. Very well researched, none of the usual hot takes and clichés.