wtfpython VS python-syntax-errors

Hi, author of the repo (https://github.com/satwikkansal/wtfpython) here, pleasantly surprised to wake up to this thread about it. The intention of the project is not to put Python in a bad light relative to other languages, the intention was to explore it more deeply through (sometimes contrived) snippets that give non-obvious outputs. I believe for a regular Python programmer, the "Slippery Slopes" section is a must-know. The first section (Strain your brain), does contain some patterns that you may not ever see in real world, the goal there is to just learn about internals. Agreed some of them are very obvious for a well-learned programmer, and some of them aren't even Python specific, it does help a lot of beginner to intermediate programmers. I remember it being given as a supplementary material in one of the CS-based course.

It is curated with something-for-everyone approach, I expect people to learn a thing or two about Python / CS after going through the snippets. I haven't updated it in a while in a major way, but looking at the feedback I'll try to organise them better, and add new snippets (I have a long personal list that I maintain) in a future release!

After reading this page:

https://github.com/satwikkansal/wtfpython?tab=readme-ov-file#-needles-in-a-haystack-

I wonder if there's any language that thought about all edge cases and avoided exceptions and such gotchas at the design level.

JS is notorious for such WTFs but even Python—which I've used for over a decade now—has surprised me countless times.

Is Haskell also like that? How about Lisps (CL, Racket, Clojure, Scheme, etc.)?

In my mind,I just automatically translate a EXPRESSION1 b EXPRESSION2 c as (a EXPRESSION1 b) and (b EXPRESSION2 c), so there's no ambiguity. But I agree, it can be VERY confusing,so I tend to write code that is easy to read without being a master. for example, think what you would have thought this evaluates to:

False is False is False. If you thought, True, you were right :)

I would recommend to take a look at one of my favourite repos for more[1].

[1]https://github.com/satwikkansal/wtfpython

See this for an explanation - https://github.com/satwikkansal/wtfpython?tab=readme-ov-file...

> `all([])` returns True since the iterable is empty.

Haven’t seen it mentioned in the replies, so here it is. Have a look at “What the f*ck Python? 😱” on GitHub: https://github.com/satwikkansal/wtfpython

https://github.com/satwikkansal/wtfpython

"Mutating the immutable" is my personal favourite - the second line of code fails with an exception despite having already succeeded:

 >>> t = ([1, 2], 5, 6)

No-op statements syntactically valid only since Python X.Y\ (90 comments)