Re: importlib2
Nick Coghlan <[email protected]> Wed, 28 May 2014 19:06:24 +1000
| Newsgroups | gmane.comp.python.import |
|---|---|
| Message-ID | <CADiSq7c0u=9nmR7hLU8CtKwwoEDhTAbm_6hwHmPzO1o36mDOOQ@mail.gmail.com> |
On 28 May 2014 14:55, "Eric Snow" <[email protected]> wrote: > > Hi all, > > Motivated at PyCon by the "pymigrate" discussions, I started > backporting importlib to 2.7. I've finally freed up some time in the > last week or so and have come close to having the project ready to > release on the cheeseshop (as importlib2). I'm hosting the repo and > bug tracker on bitbucket: > > https://bitbucket.org/ericsnowcurrently/importlib2 Awesome! > Feel free to take it for a spin. Keep in mind that any functionality > that depends on the no-longer-implicit import state (finders/path > hooks) will not work without first calling importlib2.hook.inject(). > That includes importlib2.import_module(). If you notice any other > rough corners just let me know. > > There are a few minor things I want to wrap up before officially > releasing the project, but that shouldn't take much work. In parallel > I'm going to start working on the pymigrate* project, which will > leverage importlib2 and importers to facilitate per-module enforcement > of the 2.7/3.x intersection language. Yeah, that's going to be a pretty significant project (in both senses of the word). Thanks for taking the initiative to get it moving! Cheers, Nick. _______________________________________________ Import-SIG mailing list [email protected] https://mail.python.org/mailman/listinfo/import-sig