Polyglots R Us - All Comments

re: Adventures in Meta programming in Python: im_class, import, getattribute

Ryan Svihla — Fri, 08 Jan 2010 13:09:56 GMT

@bluehavana they have that too wait a blog post :)

@chris tavares

The __call__ and __init__ methods and I figure several other special methods are not accessed.

As you said just object attributes seem to be all thats accessed.

I'll update with the correction and thanks again!

re: Adventures in Meta programming in Python: im_class, import, getattribute

Chris Tavares — Fri, 08 Jan 2010 08:05:04 GMT

Technically, __getattribute__ isn't called when a method is called, it's called when a method (or any attribute of the object) is accessed. It's original intention was to allow you to build dictionary-like objects, but turns out to be very useful for other things, as you discovered.

The net result is that if you've got a class, Foo, that implements __getattribute__, then:

o = Foo()

m = o.SomeMethod # __getattribute__ fires here

m() # not here

re: Adventures in Meta programming in Python: im_class, import, getattribute

bluehavana — Fri, 08 Jan 2010 05:23:02 GMT

Hmm... Love the __getattribute__, its like method_missing? but not.

Twitter Trackbacks for Adventures in Meta programming in Python: im_class, import, getattribute - Polyglots R Us - Los [lostechies.com] on Topsy.com

Fri, 08 Jan 2010 05:10:37 GMT

Pingback from Twitter Trackbacks for Adventures in Meta programming in Python: im_class, __import__, __getattribute__ - Polyglots R Us - Los [lostechies.com] on Topsy.com

re: Take 2: Why we use SOLID in static languages and how we get the same functionality for cheap in dynamic languages

Gil Zilberfeld — Fri, 04 Dec 2009 08:44:01 GMT

Hi,

My name is Gil Zilberfld. We’ve discussed your post on our webcast <a href="learn.typemock.com/.../episode-6-analyze-this.html">“This week in testing”</a>. We’ll be happy if you can comment, and if you like the discussion and content, let us know. And everyone else.

Thanks,

Gil Zilberfeld Typemock

re: Take 3: Python, ISP, IoC, and OCP need a fundamental rethink.

anon_anon — Thu, 03 Dec 2009 02:51:26 GMT

You might also want to look at vtd-xml for huge XML , the next generation XML processing model that is far more powerful than DOM and SAX

re: Take 3: Python, ISP, IoC, and OCP need a fundamental rethink.

Ryan Svihla — Fri, 27 Nov 2009 14:20:49 GMT

@Christian I think you're suffering from my poor English writing skills, which is sad because I've only lived in the Midwest and do not have the excuse of having proficiency in any other language.

If you keep reading the line passed the three periods in a row the rest of the statement clears it up, I'll respond here without the three periods but a comma instead.

"100% DI’d code will be more effort to maintain because it would be in C# too, if not for that fact the language is so “structured” that the flexibility and testability benefits gained far outweigh the slightly increased cost (which is only brought down with the awesomeness of auto registering components). In a language already with flexibility and testability whether you use DI or not AND without auto registering IoC containers the cost to maintain a full DI code base is I’d argue unacceptable."

So for example when I use IoC, I autoregister almost everything. My registration lines are maybe 10 or 12 for large code bases, and those are to handle the edge of the system typically.

When I didn't autoregister and instead maintained huge XML files (or explicit code later) the pain was quite severe. I was still willing to have this because the benefits in flexibility still far outstripped the cost. But trust me I was VERY happy to have auto-registration later on, its something the Java community has completely missed the boat on from what I've seen.

re: Take 3: Python, ISP, IoC, and OCP need a fundamental rethink.

Christian — Fri, 27 Nov 2009 11:40:41 GMT

"100% DI’d code will be more effort to maintain because it would be in C# too"

I think this is a throw away comment and do not agree. Could you explain what you mean further?

To me I think having all you dependencies created in a single place is vastly easier then having them littered through the codebase.

re: Take 3: Python, ISP, IoC, and OCP need a fundamental rethink.

Ryan Svihla — Tue, 24 Nov 2009 03:44:05 GMT

@louis yeah and from what I've seen Bob Martin himself has gone the dynamic language route (no idea what that means for his interpretation of SOLID).

@Daniel I think there is a kernel of truth, but its more like you can't be a great chef until you can make a proper omelet. You have to understand the SOLID principles well enough to know when to apply them and Bob Martin has often talked about them not being a dogmatic thing.

re: Take 3: Python, ISP, IoC, and OCP need a fundamental rethink.

Daniel — Mon, 23 Nov 2009 19:43:09 GMT

SOLID principles are akin to the step-by-step process McDonald's employees must follow to create a hamburger. A great chef doesn't need those rules, but in lieu of talent they ensure a consistent product. It might be worth asking if you want a Big Mac...or something better.

re: Take 3: Python, ISP, IoC, and OCP need a fundamental rethink.

Louis Salin — Mon, 23 Nov 2009 14:56:30 GMT

Awesome series of articles, Ryan. I've been thinking about the same thing (applying SOLID to dynamic languages) and I'm happy to see that you've gone into the same direction yourself.

I never thought about monkey patching as a useful way to do dependency injection, which, incidentally, still remains dependency injection, no? It's still a technique you can use that you must remain aware of. So maybe SOLID becomes SLID? :)

Take 3: Python, ISP, IoC, and OCP need a fundamental rethink … MoinMoin Wiki

Take 3: Python, ISP, IoC, and OCP need a fundamental rethink … MoinMoin Wiki — Sat, 21 Nov 2009 16:12:35 GMT

Pingback from Take 3: Python, ISP, IoC, and OCP need a fundamental rethink … MoinMoin Wiki

Twitter Trackbacks for Take 3: Python, ISP, IoC, and OCP need a fundamental rethink. - Polyglots R Us - Los Techies : Blogs about [lostechies.com] on Topsy.com

Sat, 21 Nov 2009 07:47:15 GMT

Pingback from Twitter Trackbacks for Take 3: Python, ISP, IoC, and OCP need a fundamental rethink. - Polyglots R Us - Los Techies : Blogs about [lostechies.com] on Topsy.com

re: I recant my IoC! IoC containers in dynamic languages are silly.

Petar Shomov — Fri, 20 Nov 2009 23:27:01 GMT

Hi Ryan,

Thank you for taking the time to asnwer my concerns. I find that all of the resolutions you offered were too much sacrificy for my taste and actually summarize why I always prefer DI over Service Locator(I am not sure what I was thinking but I realized outputselect and saveoutput methods are actually participatng in a service locator pattern. Have to read blogs in the morning, when fresh ...). Anyways, thanx for the discussion, I am always curios about other people's perspective, so keep these posts coming ;)

re: Take 2: Why we use SOLID in static languages and how we get the same functionality for cheap in dynamic languages

Julian Birch — Fri, 20 Nov 2009 18:21:43 GMT

Hi Ryan, good article (even if I disagree). I'm afraid my response was rather longer than the average comment.

www.colourcoding.net/.../dynamic-languages-and-solid-principles.aspx

Julian.

Polyglots R Us - All Comments

re: Adventures in Meta programming in Python: im_class, __import__, __getattribute__

re: Adventures in Meta programming in Python: im_class, __import__, __getattribute__

re: Adventures in Meta programming in Python: im_class, __import__, __getattribute__

Twitter Trackbacks for Adventures in Meta programming in Python: im_class, __import__, __getattribute__ - Polyglots R Us - Los [lostechies.com] on Topsy.com

re: Take 2: Why we use SOLID in static languages and how we get the same functionality for cheap in dynamic languages

re: Take 3: Python, ISP, IoC, and OCP need a fundamental rethink.

re: Take 3: Python, ISP, IoC, and OCP need a fundamental rethink.

re: Take 3: Python, ISP, IoC, and OCP need a fundamental rethink.

re: Take 3: Python, ISP, IoC, and OCP need a fundamental rethink.

re: Take 3: Python, ISP, IoC, and OCP need a fundamental rethink.

re: Take 3: Python, ISP, IoC, and OCP need a fundamental rethink.

Take 3: Python, ISP, IoC, and OCP need a fundamental rethink … MoinMoin Wiki

Twitter Trackbacks for Take 3: Python, ISP, IoC, and OCP need a fundamental rethink. - Polyglots R Us - Los Techies : Blogs about [lostechies.com] on Topsy.com

re: I recant my IoC! IoC containers in dynamic languages are silly.

re: Take 2: Why we use SOLID in static languages and how we get the same functionality for cheap in dynamic languages

re: Adventures in Meta programming in Python: im_class, import, getattribute

re: Adventures in Meta programming in Python: im_class, import, getattribute

re: Adventures in Meta programming in Python: im_class, import, getattribute

Twitter Trackbacks for Adventures in Meta programming in Python: im_class, import, getattribute - Polyglots R Us - Los [lostechies.com] on Topsy.com