<br><br><div class="gmail_quote">On Fri, May 4, 2012 at 12:00 PM, <a href="mailto:fwierzbicki@gmail.com">fwierzbicki@gmail.com</a> <span dir="ltr"><<a href="mailto:fwierzbicki@gmail.com" target="_blank">fwierzbicki@gmail.com</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 Fri, May 4, 2012 at 7:34 AM, Barry Warsaw <<a href="mailto:barry@python.org">barry@python.org</a>> wrote:<br>
> It's also not true even today. At our PEP 420 sprint we noticed importlib<br>
> does something like this to create new modules:<br>
><br>
> >>> type(sys)('foo')<br>
><br>
> That module isn't a built-in and doesn't have an __file__. It also<br>
> doesn't have an __loader__, but oh well.<br>
><br>
> (BTW, Brett, that's pretty clever. :)<br>
</div>Too clever for Jython at them moment :) -- which leads me to ask:<br>
Should I consider this a a feature of the sys module?</blockquote><div><br></div><div>No, this is an ability of types.ModuleType (which I don't have access to in importlib, so I just inlined the call). This works for any module in CPython.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> It doesn't look<br>
too hard to do, and I really want importlib to work when Jython starts<br>
on Jython3 (I'm hoping to seriously start that this summer - Jython<br>
2.7 is progressing well).<br></blockquote><div><br></div><div> I've actually been meaning to email the various VMs to have them look over importlib to see if there are any sticking points that are obvious so we can fix them now instead of waiting until a point release when the first VM other than CPython tries to use importlib.</div>
</div>