I don't use them anymore, but I'm curious about others opinions on this\nlist...\n\nThe more time I spend in Python, discovering what "Pythonic" code is and\nsuch, it seems that I throw away much in terms of academic learnings as\nfar as "OOP correctness" goes. In doing so, I find that, in general,\noverall LOC (yes, I'm aware that this is a poor metric to judge anything\non), readability and overall quality of code seems to go up. Yes, you\ngive the user much more rope to hang themselves with making the general\nassumption that the user knows what they're doing, but we're all\nconsenting adults here after all, right? ;)\n\nAs an example, I initially had an OAuth 2.0 client library that was\nroughly 450 LOC (using ABCs, adapter patterns for the various flows,\netc). Dropping this for a more "Pythonic" (at least, what my\ninterpretation of Pythonic code is) brought the entire library down to\n55 LOC. Having said that, the decline in LOC and overall grok-ability\nwasn't entirely due to moving away from ABCs and dropping the use of\nadapters, but it did have quite a bit to do with it).\n\nAs such, I see ABCs as somewhat of an anti-pattern in the Python world.\nThe concept is obviously essential in non-duck-typed language using\nstrict OOP, but does it *really* belong in Python?