On Wed, 2013-04-17 at 15:31 +0200, Vladimir Keleshev wrote:
> Hi Ian,
>
> I'm ready to assist you with integrating pep257 into flake8. Do you
> plan to vendorize it or make it a dependency? `Error` is the right
> class to look for. `__str__` formats the error. The default format
> looks like:
>
On 4/15/13 8:59 PM, Vladimir Keleshev wrote:
Hi Ian,
I'm actually on the mailing list as well (since maybe 2 weeks ago).
You might remember my email about proposing a common format for error
messages. I think it's a great idea to coordinate development of our
static-analysis tools. Adding pep2
Hi Ian, I'm ready to assist you with integrating pep257 into flake8. Do you plan to vendorize it or make it a dependency? `Error` is the right class to look for. `__str__` formats the error. The default format looks like: path/file.py:14:4: PEP257 Class docstrings should have 1 blank line aroun
On Wed, Apr 17, 2013 at 8:49 AM, Ian Cordasco
wrote:
> On Mon, Apr 15, 2013 at 2:59 PM, Vladimir Keleshev
> wrote:
>> Hi Ian,
>>
>> I'm actually on the mailing list as well (since maybe 2 weeks ago). You
>> might remember my email about proposing a common format for error messages.
>> I think it'
On Mon, Apr 15, 2013 at 2:59 PM, Vladimir Keleshev
wrote:
> Hi Ian,
>
> I'm actually on the mailing list as well (since maybe 2 weeks ago). You
> might remember my email about proposing a common format for error messages.
> I think it's a great idea to coordinate development of our static-analysis
Hi Ian, I'm actually on the mailing list as well (since maybe 2 weeks ago). You might remember my email about proposing a common format for error messages. I think it's a great idea to coordinate development of our static-analysis tools. Adding pep257 to flake8 might be a good idea. Shall we call i
