Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/cosmologicon/pywat

Python wats
https://github.com/cosmologicon/pywat

Last synced: about 2 months ago
JSON representation

Python wats

Awesome Lists containing this project

README 

        
# Python wats



A "wat" is what I call a snippet of code that demonstrates a counterintuitive edge case of a programming language. (The name comes from [this excellent talk by Gary Bernhardt](https://www.destroyallsoftware.com/talks/wat).) If you're not familiar with the language, you might conclude that it's poorly designed when you see a wat. Often, more context about the language design will make the wat seem reasonable, or at least justified.



Wats are funny, and learning about a language's edge cases probably helps you with that language, but I don't think you should judge a language based on its wats. (It's perfectly fine to judge a language, of course, as long as it's an *informed* judgment, based on whether the language makes it difficult for its developers to write error-free code, not based on artificial, funny one-liners.) This is the point I want to prove to Python developers.



If you're a Python developer reading these, you're likely to feel a desire to put them into context with more information about how the language works. You're likely to say "Actually that makes perfect sense if you consider how Python handles *X*", or "Yes that's a little weird but in practice it's not an issue." And I completely agree. Python is a well designed language, and these wats do not reflect badly on it. You shouldn't judge a language by its wats.



## The Python wat quiz



Are you unimpressed by these wats? Do you think these edge cases are actually completely intuitive? Try your hand at [the Python wat quiz](https://github.com/cosmologicon/pywat/blob/master/quiz.md)!



## The wats



### The undocumented [converse implication](https://en.wikipedia.org/wiki/Converse_implication) operator



```python

>>> False ** False == True

True

>>> False ** True == False

True

>>> True ** False == True

True

>>> True ** True == True

True

```



### Mixing numerical types



```python

>>> x = (1 << 53) + 1

>>> x + 1.0 < x

True

```



Think this is just floats being weird? Floats are involved, but it's not their fault this time. [Check out the explanation to see why.](https://github.com/cosmologicon/pywat/blob/master/explanation.md#mixing-numerical-types)



### Operator precedence?



```python

>>> (False == False) in [False]

False

>>> False == (False in [False])

False

>>> False == False in [False]

True

```



[Source](https://www.reddit.com/r/programming/comments/3cjjgp/why_does_return_the_string_10/csxak65).



### Iterable types in comparisons



```python

>>> a = [0, 0]

>>> (x, y) = a

>>> (x, y) == a

False

```



```python

>>> [1,2,3] == sorted([1,2,3])

True

>>> (1,2,3) == sorted((1,2,3))

False

```



[See the explanation if you think this is not a wat.](https://github.com/cosmologicon/pywat/blob/master/explanation.md#iterable-types-in-comparisons)



### Types of arithmetic operations



The type of an arithmetic operation cannot be predicted from the type of the operands alone. You also need to know their value.



```python

>>> type(1) == type(-1)

True

>>> 1 ** 1 == 1 ** -1

True

>>> type(1 ** 1) == type(1 ** -1)

False

```



### Fun with iterators



```python

>>> a = 2, 1, 3

>>> sorted(a) == sorted(a)

True

>>> reversed(a) == reversed(a)

False

```



```python

>>> b = reversed(a)

>>> sorted(b) == sorted(b)

False

```



### Circular types



```python

>>> isinstance(object, type)

True

>>> isinstance(type, object)

True

```



[Source](https://www.reddit.com/r/Python/comments/3c344g/so_apparently_type_is_of_type_type/csrwwyv).



### `extend` vs `+=`



```python

>>> a = ([],)

>>> a[0].extend([1])

>>> a[0]

[1]

>>> a[0] += [2]

Traceback (most recent call last):

  File "", line 1, in 

TypeError: 'tuple' object does not support item assignment

>>> a[0]

[1, 2]

```



### Indexing with floats



```python

>>> [4][0]

4

>>> [4][0.0]

Traceback (most recent call last):

  File "", line 1, in 

TypeError: list indices must be integers, not float

>>> {0:4}[0]

4

>>> {0:4}[0.0]

4

```



### `all` and emptiness



```python

>>> all([])

True

>>> all([[]])

False

>>> all([[[]]])

True

```



### `sum` and strings



```python

>>> sum("")

0

>>> sum("", ())

()

>>> sum("", [])

[]

>>> sum("", {})

{}

>>> sum("", "")

Traceback (most recent call last):

  File "", line 1, in 

TypeError: sum() can't sum strings [use ''.join(seq) instead]

```



### NaN-related wats



```python

>>> x = float("nan")

>>> y = float("nan")

>>> x == x

False

>>> [x] == [x]

True

>>> [x] == [y]

False

```



[Source](https://github.com/cosmologicon/pywat/issues/22).



```python

>>> x = float("nan")

>>> len({x, x, float(x), float(x), float("nan"), float("nan")})

3

>>> len({x, float(x), float("nan")})

2

```



```python

>>> x = float("nan")

>>> (2 * x).imag

0.0

>>> (x + x).imag

0.0

>>> (2 * complex(x)).imag

nan

>>> (complex(x) + complex(x)).imag

0.0

```



## Explanations



Want to learn more about the inner workings behind these wats? Check out the [explanation page](https://github.com/cosmologicon/pywat/blob/master/explanation.md) for clarity.