Python already supports extra importers written in Python, by adding them to sys.meta_path. I'd prefer to stick to widely supported Python techniques than invent new ones.
In Python 3 the import system is rewritten Python anyway (importlib) although I still need to update the IronPython 3 branch to actually use it. There's a bit of a bootstrapping problem to be dealt with. - Jeff On Fri, Dec 11, 2015 at 5:12 AM, Benedikt Eggers <begg...@spiegelburg.net> wrote: > Hello, > > > > currently I am struggling with the idea, to implement some generic > importer interface into ironpython. My aim is, > > to make it easier for people, to provide their own logic, for loading > scripts, modules, packages. For example from databases > > or some webservice if needed. May idea was, to extend the python context > with some list, which holds instances of IGenericImport. > > > > All generic importers will be called in FindImporterForPath. If a generic > importer can be used to resolve some path, it will be responsible > > to import all needed files, … > > > > When this is something useful, I would make some plans for implementation. > > > > Thank you for reading the mail! > > > > With best regards, > > > > B. Eggers > > _______________________________________________ > Ironpython-users mailing list > Ironpython-users@python.org > https://mail.python.org/mailman/listinfo/ironpython-users > >
_______________________________________________ Ironpython-users mailing list Ironpython-users@python.org https://mail.python.org/mailman/listinfo/ironpython-users
