<br><br><div class="gmail_quote">On Tue, Feb 7, 2012 at 15:24, Barry Warsaw <span dir="ltr"><<a href="mailto:barry@python.org">barry@python.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Brett, thanks for persevering on importlib! Given how complicated imports are<br>
in Python, I really appreciate you pushing this forward. I've been knee deep<br>
in both import.c and importlib at various times. ;)<br>
<div class="im"><br>
On Feb 07, 2012, at 03:07 PM, Brett Cannon wrote:<br>
<br>
>One is maintainability. Antoine mentioned how if change occurs everyone is<br>
>going to have to be able to fix code in importlib, and that's the point! I<br>
>don't know about the rest of you but I find Python code easier to work with<br>
>than C code (and if you don't you might be subscribed to the wrong mailing<br>
>list =). I would assume the ability to make changes or to fix bugs will be<br>
>a lot easier with importlib than import.c. So maintainability should be<br>
>easier when it comes to imports.<br>
<br>
</div>I think it's *really* critical that importlib be well-documented. Not just<br>
its API, but also design documents (what classes are there, and why it's<br>
decomposed that way), descriptions of how to extend and subclass, maybe even<br>
examples for doing some typical hooks. Maybe even a guided tour or tutorial<br>
for people digging into importlib for the first time.<br></blockquote><div><br></div><div>That's fine and not difficult to do.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
>So, that is the positives. What are the negatives? Performance, of course.<br>
<br>
</div>That's okay. Get it complete, right, and usable first and then unleash the<br>
Pythonic hoards to bang on performance.<br>
<div class="im"><br>
>IOW I really do not look forward to someone saying "importlib is so much<br>
>slower at importing a module containing ``pass``" when (a) that never<br>
>happens, and (b) most programs do not spend their time importing but<br>
>instead doing interesting work.<br>
<br>
</div>Identifying the use cases are important here. For example, even if it were a<br>
lot slower, Mailman wouldn't care (*I* might care because it takes longer to<br>
run my test, but my users wouldn't). But Bazaar or Mercurial users would care<br>
a lot.<br></blockquote><div><br></div><div>Right, which is why I'm looking for some agreed upon, concrete benchmark I can use which isn't fluff.</div><div><br></div><div>-Brett</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
-Barry<br>
_______________________________________________<br>
Python-Dev mailing list<br>
<a href="mailto:Python-Dev@python.org">Python-Dev@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/python-dev" target="_blank">http://mail.python.org/mailman/listinfo/python-dev</a><br>
Unsubscribe: <a href="http://mail.python.org/mailman/options/python-dev/brett%40python.org" target="_blank">http://mail.python.org/mailman/options/python-dev/brett%40python.org</a><br>
</blockquote></div><br>