[Import-SIG] importlib2

Nick Coghlan ncoghlan at gmail.com
Wed May 28 16:41:54 CEST 2014

On 29 May 2014 00:19, Eric Snow <ericsnowcurrently at gmail.com> wrote:
> 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.

IIRC, it came out of one of our conversation with Steve Dower, and it
was more a matter of "do both" rather than one or the other. The other
advantage of the runtime model was being able to turn on -3 warnings.


Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Import-SIG mailing list