Travis build failure is unrelated.

The documentation says ... if my_backend.pyis a matplotlib backend in yourPYTHONPATH ... to me this implies the import is meant to be absolute already.

Yeah -- I think absolute has certainly always been the intent, even if not the effect of the code.

Certainly... I just want a comment (or something) right there above it to explain the "0" parameter being passed to the __import__ function. It isn't like we use __import__ everyday. Lets imagine an incorrect value was placed there today, with no comment. A year from now, someone comes along and sees what the documentation says, and sees what the import does, and will probably be afraid to fix it because "it was set that way for some reason, right?"

Maybe it is just me being nuts...

No, you're being perfectly reasonable. I'll write something in. 

Andrea

—
Sent from Mailbox for iPhone

On Tue, Aug 27, 2013 at 11:52 PM, Benjamin Root notifications@github.com
wrote:

Certainly... I just want a comment (or something) right there above it to explain the "0" parameter being passed to the __import__ function. It isn't like we use __import__ everyday. Lets imagine an incorrect value was placed there today, with no comment. A year from now, someone comes along and sees what the documentation says, and sees what the import does, and will probably be afraid to fix it because "it was set that way for some reason, right?"

Maybe it is just me being nuts...

Reply to this email directly or view it on GitHub:
#2335 (comment)