<br><br><div class="gmail_quote">On Tue, Apr 17, 2012 at 13:39, Antoine Pitrou <span dir="ltr"><<a href="mailto:solipsis@pitrou.net">solipsis@pitrou.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Tue, 17 Apr 2012 11:41:32 -0400<br>
Brett Cannon <<a href="mailto:brett@python.org">brett@python.org</a>> wrote:<br>
><br>
> Actually Cython would help with a subtle maintenance burden of maintaining<br>
> *any* C code for import. Right now,<br>
> Python/import.c:PyImport_ImportModuleLevelObject() is an accelerated C<br>
> version of importlib.__import__() through checking sys.modules, after which<br>
> it calls into the Python code. Cython would do away with that C<br>
> acceleration code (which I have already had to modify once and Antoine<br>
> found a couple refleaks in).<br>
<br>
</div>Would it? That's assuming Cython would be smart enough to do the<br>
required optimizations.<br></blockquote><div><br></div><div>Yes, it is an assumption I'm making. I also assume we wouldn't make a change like this w/o taking the time to run importlib through Cython and seeing how the performance numbers come out.</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>
Regards<br>
<span class="HOEnZb"><font color="#888888"><br>
Antoine.<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<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>
</div></div></blockquote></div><br>