{"id":163,"date":"2007-07-23T23:06:27","date_gmt":"2007-07-24T06:06:27","guid":{"rendered":"https:\/\/dubinko.info\/blog\/2007\/07\/23\/prototypical-inheritance-in-python\/"},"modified":"2007-07-23T23:06:27","modified_gmt":"2007-07-24T06:06:27","slug":"prototypical-inheritance-in-python","status":"publish","type":"post","link":"https:\/\/dubinko.info\/blog\/2007\/07\/prototypical-inheritance-in-python\/","title":{"rendered":"Prototypical inheritance in Python"},"content":{"rendered":"

Based on Doug Crockford’s chapter in Beautiful Code<\/a>, I wanted to take a crack at implementing Top Down Operator Precedence<\/a> in Python. After all, Python and JavaScript are quite similar, right?<\/p>\n

Not really. As you can imagine, Doug’s code makes great use of JavaScript’s strengths, in this case the ability to assign new methods to any object. For an initial version, I wanted to make the Python version behave the same way, as opposed to a deeper redesign that would be more pythonic. (That would come later.)
\nMy initial approach was a __getattr__<\/code> method that consisted simply of return getattr(self.prototype, name)<\/code>. When reattaching a new method to an instance, I needed an extra wrapper, done through a wrap<\/code> method which consisted of return new.instancemethod(method, self, self.__class__)<\/code>. It would be used like this: obj.method = obj.wrap(some_func)<\/code>.<\/p>\n

This caused a subtle problem that took me a while to track down. In JavaScript, any function can reference the built-in this<\/code> variable, which works whether the function is bound to some specific object or not. (Even global functions are bound to the global object.) But Python doesn’t have such a keyword. The language prefers the explicit, and uses a explicitly passed parameter, called by convention self<\/code>. The call to wrap a specific function also had the effect of binding the self<\/code> parameter to that particular object; even if it later became a prototype for some other object. This manifested itself as all kinds of broken behavior. For example, the original code has a global scope<\/code> object, and every time a new scope was entered, the global pointed to a newer object that kept a reference to the rest of the scope chain. But in the object’s methods, self<\/code> pointed to something different than the global. Messy.<\/p>\n

Before I get into solutions, I’d like to see what readers say. How would you go about implementing prototypical inheritance in Python? And what is a more pythonic way to accomplish the same thing? Comment below. Thanks! -m<\/p>\n","protected":false},"excerpt":{"rendered":"

Based on Doug Crockford’s chapter in Beautiful Code, I wanted to take a crack at implementing Top Down Operator Precedence in Python. After all, Python and JavaScript are quite similar, right? Not really. As you can imagine, Doug’s code makes great use of JavaScript’s strengths, in this case the ability to assign new methods to…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[24,22,1],"tags":[],"class_list":["post-163","post","type-post","status-publish","format-standard","hentry","category-python","category-software","category-stuff"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t