{"id":107,"date":"2008-05-27T09:22:42","date_gmt":"2008-05-27T15:22:42","guid":{"rendered":"http:\/\/www.philhassey.com\/blog\/2008\/05\/27\/meta-methods-python-vs-tinypy\/"},"modified":"2008-05-27T09:23:21","modified_gmt":"2008-05-27T15:23:21","slug":"meta-methods-python-vs-tinypy","status":"publish","type":"post","link":"https:\/\/www.philhassey.com\/blog\/2008\/05\/27\/meta-methods-python-vs-tinypy\/","title":{"rendered":"meta-methods: python vs tinypy"},"content":{"rendered":"

Man, could I have even thought of a title that sounds dustier? It just screams “Get ready for the boring lecture of the year folks.” I should totally re-name this post to something like “putting your brain through a blender .. FOR FUN!” Or maybe I should have gone the pretentious route and named it something like “Analysis of modern programming meta-method paradigms.” Actually, that sounds even dustier than my original title. At least my original one falsely implies that there is some competition going on in this post by my use of the “vs”.<\/p>\n

Here’s how python does it:<\/p>\n

class X:
\n    def __get__(self,k): return “OK”<\/p>\n

Here’s how tinypy does it:<\/p>\n

class MetaX:
\n    def __get__(self,k): return “OK”
\nclass X:
\n    def __init__(self): setmeta(self,MetaX)<\/p>\n

Okay .. so .. the python way is WAY more readable. Nice \ud83d\ude42 So let me remember if there was a good reason for doing it a different way in tinypy … I think the answer is “maybe” ? Here’s what I can come up with:<\/p>\n