repr(...) doesn't work the way you expect (intermediate - advanced) anthony explains

[@AceofSpades5757]

But wait... That's exactly how I would expect it to work...

[@anthonywritescode]

YOU KNOW TOO MUCH

[@theeFaris]

I could watch this all day

[@anthonywritescode]

hah well fortunately the playlist is about ~60 hours of content :)

[@sillybuttons925]

twitch!

[@SO-dl2pv]

Instead of using a lambda function, you could use (can't render correctly on a youtube comment):
"type(exit).__repr__ = type(exit).__call__"

[@alexeyzhurov7747]

I didn't need this information ... before I watched this video

[@erwan5112]

I once spent a lot of time trying to implement lazy loading by modifying a class __getattribute__ so that it would initialize the instance and then set the instance __getattribute__ to object.__getattribute__ ... Obviously it did not work, as instance.__getattribute__ is never called, I wish I had known the behavior before, it would have prevented me from loosing a lot of time 😄

[@anthonywritescode]

yeah making proxy objects is pretty tricky

[@con-f-use]

Any reason why you did `lambda: exit()` instead of just `exit` on the left hand side of `type(exit).__repr__ = ...`?

[@anthonywritescode]

it's `type(exit).__repr__ = lambda self: exit()` -- need to have a parameter for `self`

[@con-f-use]

@@anthonywritescode ah right, it would work without the lambda because exit does take an argument, but what is passed as self would be taken as an exit-code. Thanks!