[Import-SIG] importlib2

[Eric Snow]

On Wed, May 28, 2014 at 7:44 AM, Brett Cannon <bcannon at gmail.com> wrote:
> You'll have to refresh my memory because there were a lot of ideas tossed
> out at PyCon: why an importer and not some custom rules for pylint? E.g. I
> can see requiring that either ``from __future__ import unicode_literals`` or
> every string literal being marked with u or b being a rule, but I don't see
> the exact benefit of that over an importer (I realize that a per-file thing
> is desired, but tooling for that should be possible as well).

To be honest, I don't remember exactly.  Maybe a linter would be
sufficient, though I could swear there was some reason it wasn't.
I'll consider that.

>
> Anyway, this discussion should probably happen on the python-porting list
> since that's the audience more interested in this topic. =)

I was actually going to take it over to python-ideas (or python-dev)
considering the possible impact of the tool.  I hadn't even thought
about python-porting.  That will be a good place to start. :)

-eric