truth/falsity is more general than that in python, so bools aren't really necessary.
As for why, 0 is false, nonzero is true (not 1, any non-zero). So false is 'nothing there' and true is 'something is there'. This generalises to other structures, an empty list is nothing (ie. false) a non-empty list is not-nothing so is true so you can do
>>> y = [23, 24, 25]
>>> while y:
... print(y)
... y = y[1:]
...
[23, 24, 25]
[24, 25]
[25]
Ditto loadsa other things.I guess this was a lisp inheritance.
It’s not that clear cut. If you assign d[True] and then d[1] you overwrite because True hashes to 1, not because 1 is a truthy value. If you try writing to d[2] you don’t overwrite d[True].
In any case this Feels like an odd case where python is sort of doing something similar to implicit type conversion which goes against the zen of python.
This whole mutating or not mutating thing was a huge headache when starting python and still causes gotchas.
R is supposedly the “poorly designed” programming language that data scientists may use instead of python, but I’ve never had such problems in R.
Well, I'd say 1) immutability is expensive[0] and 2) mutability is sometimes simpler and clearer than immutability for some algorithms IMO. So I'd want python to have both.
Today's passion for 'immutable everything' is going to burn out pretty quick as it's great but being used too much and without recognising its cost. IMO again.
[0] if naively implemented, and it so often is.
So my point is not “python is hard because of mutability” it’s that pythons mutability really gets in the way of the beginner and causes lots of gotchas for even well experienced developers.
ok
> ...it’s that pythons mutability really gets in the way of the beginner and causes lots of gotchas for even well experienced developers
So python is hard because of mutability? (well, harder anyway).
The fact is, if python had immutability it'd be semantically simpler. Unquestionably (I'd claim). But that comes at a performance cost, so mutability is allowed. That's when we get these confusions of what an operation does (because the semantics get non-simple). My point is either way we pay a price.
Anyway I have a feeling I may be misconstruing your point, sorry if that's so.
Use any/all instead? <https://stackoverflow.com/questions/31099561/test-if-all-ele.... More general (see my other post), shorter and clearer?
sum(list_of_bools) / len(list_of_bools)
and np_array_of_bools.mean()
There is probably a more correct way, but I enjoy it.Rest of the points I was already familiar with from various experiences. To me, they are just filler for the article.
1. Caused by confusing reference semantics and value semantics, which is pretty much inevitable when a fundamental data type is mutable.
2. Boolean is a subclass of Integer, because... why?
3. Same problem as #1.
4. Once again, beginners have no understanding of reference vs. value semantics, and why should they?
5. Default arguments of a function are evaluated just once, because... why? This one just seems crazy to me. It turns default arguments into stateful globals, so an innocent-looking function suddenly exhibits unpredictable behavior.