Not that early here either, so I could also be confusing myself, but I
don't think this is an issue.
flake8 uses the flake8.engine.get_style_guide() function [1] which takes in
``config_file=DEFAULT_CONFIG`` in just about every place it's called (e.g.
[2]) which in pep8 gets passed explicitly to `
On Wed, Mar 18, 2015 at 12:50 AM, Ian Lee wrote:
> Yes, it wasn't an exact reversion of just that change (though perhaps that
> would be a better way to go about it).
>
> The logic that you're looking for (if I'm reading this right) is that last
> bit of the diff you posted (
> https://github.com
Yes, it wasn't an exact reversion of just that change (though perhaps that
would be a better way to go about it).
The logic that you're looking for (if I'm reading this right) is that last
bit of the diff you posted (
https://github.com/jcrocholl/pep8/compare/1.5.7...435d1cbf995a659a82d1d4b42d25e3
On Wed, Mar 18, 2015 at 12:17 AM, Ian Lee wrote:
> Hi All --
>
> I just pushed a commit [1] to the pep8 repo that contains what I hope is a
> fix for the issues with pep8 / flake8 config files that arose from the way
> that pep8 #368 was handled, e.g. [2] (I think, I'm getting 500 errors when
> I
Hi All --
I just pushed a commit [1] to the pep8 repo that contains what I hope is a
fix for the issues with pep8 / flake8 config files that arose from the way
that pep8 #368 was handled, e.g. [2] (I think, I'm getting 500 errors when
I try to few issues on the flake8 repo, but I'm hoping that is
