Re: Ironpython 2.7.9 ImportException: 'No Module Named errno' when importing another module in .NET application
toggle quoted messageShow quoted text
I'm not sure why removing the site-packages from the search paths would have an effect on loading IronPython.Modules since it occurs in within Python.CreateEngine(). You can check that it gets loaded by adding something like:
Debug.Assert(AppDomain.CurrentDomain.GetAssemblies().Select(x => x.GetName().Name).Contains("IronPython.Modules"));
right after you create the engine.
Are you sure "import jinja2" was still failing with the ImportError and not something else? Note that jinja2 will fail with a SyntaxError if you try to import it from IronPython. You'll have to tweak lexer.py to get it working.
On Fri, Nov 30, 2018 at 12:40 PM micoo via Groups.Io <firstname.lastname@example.org> wrote: