wtfpython

In a similar vein you may like "WTF Python: Exploring and understanding Python through surprising snippets": https://github.com/satwikkansal/wtfpython HN thread: https://news.ycombinator.com/item?id=26097732 (163 comments) PS: found with a site I'm building: https://discussions.xojoc.pw/?q=Understanding+Python+through...

> But most "wtfpython" things don't actually affect people using the language Plenty do though. I've passed that page onto co-workers a lot, back when the list was smaller, and almost every time they've found something on the page that explains a bit of weirdness with Python that they'd just dismissed as buggy behavior and avoided touching. The ones I remember them mentioning: https://github.com/satwikkansal/wtfpython#-mutating-the-immu... https://github.com/satwikkansal/wtfpython#-beware-of-default... And I multiple times I've had to explain the difference between references / shallow copy / deep copy to bootcampers, which falls under https://github.com/satwikkansal/wtfpython#-a-tic-tac-toe-whe...

Python had their smearing campaign claiming TIOOWTDI against Perl's TIMTOWTDI, and dubious claim's of sigils (`@$`) hurt readability. But once Python had the ecosystem going, it brought back `@`, `{}`, numerous `_`, fanciful `:=`. And, of course, there always is more than one way to do it in Python. Python's "easy to use" is just a lie, https://github.com/satwikkansal/wtfpython The common lisp CFFI module is nothing short of Python's. But, I know, people hate to put their `(` in front of their function names, and people hate to omit `,` between there function arguments.

Yes, of course. BTW, that's not the "biggest" WTF feature; it's just my favorite. There's a long list of WTF features here: https://github.com/satwikkansal/wtfpython Otherwise, I agree, it's a pretty good going :-)

I always have been and always will be against the walrus operator. I don't care how much anyone tries me to sell it on its elegance. There's just no _need_. It's already the #1 example of wtfpython https://github.com/satwikkansal/wtfpython#-first-things-firs... /rant. Those kind of features are going to keep coming anyway, I'm afraid.

You're talking about something different. The parent comment is about mutable default arguments are shared between all calls to that function [1], but you seem to be talking about functions defined in for loops all sharing a reference to the same variable [2]. [1] https://github.com/satwikkansal/wtfpython#-beware-of-default... [2] https://github.com/satwikkansal/wtfpython#-loop-variables-le... > In this example it's just a constant but this trick is often used with mutable defaults. Your example doesn't work with mutable defaults. Ironically it falls into the trap the parent comment was referring to! def main(): funcs = [] arg = [] for x in range(10) arg.append(x) def f(arg=arg): return arg funcs.append(f) print(*[f() for f in funcs], sep="\n")

I wasted recently plenty of time debugging that one - and I ended it by removing default arguments. And I was sure that it was cause by a bug in my code, thanks for pointing this out - now I know what caused this https://github.com/satwikkansal/wtfpython#-beware-of-default...