<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/python-packages/flake8.git/src/flake8/formatting/base.py, branch 3.2.0</title>
<subtitle>gitlab.com: pycqa/flake8.git
</subtitle>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/flake8.git/'/>
<entry>
<title>Merge branch 'master' into 'master'</title>
<updated>2016-10-25T21:34:43+00:00</updated>
<author>
<name>Ian Cordasco</name>
<email>graffatcolmingov@gmail.com</email>
</author>
<published>2016-10-25T21:34:43+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/flake8.git/commit/?id=a9e15afbf50b3181af45a64f5736d432731eb40d'/>
<id>a9e15afbf50b3181af45a64f5736d432731eb40d</id>
<content type='text'>

Add --tee option to split report output stream.

The `--tee` option allows the linter report to be written to stdout, even
though it is being redirected to a file with the` --output-file` option.
This is useful if I want to store the report in a separate file for later
analysis but also be able to print the output on screen (e.g when running
in a CI environment).

See merge request !90</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>

Add --tee option to split report output stream.

The `--tee` option allows the linter report to be written to stdout, even
though it is being redirected to a file with the` --output-file` option.
This is useful if I want to store the report in a separate file for later
analysis but also be able to print the output on screen (e.g when running
in a CI environment).

See merge request !90</pre>
</div>
</content>
</entry>
<entry>
<title>Open our output file in append mode always</title>
<updated>2016-07-29T23:14:14+00:00</updated>
<author>
<name>Ian Cordasco</name>
<email>graffatcolmingov@gmail.com</email>
</author>
<published>2016-07-29T22:18:47+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/flake8.git/commit/?id=e93aad6043f870d04648e7e0af983248ec60c9ef'/>
<id>e93aad6043f870d04648e7e0af983248ec60c9ef</id>
<content type='text'>
This avoid overwriting portions of our log output when using Flake8
in verbose mode.

Closes #193
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This avoid overwriting portions of our log output when using Flake8
in verbose mode.

Closes #193
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix zero-indexed column numbering</title>
<updated>2016-07-27T00:45:05+00:00</updated>
<author>
<name>Ian Cordasco</name>
<email>graffatcolmingov@gmail.com</email>
</author>
<published>2016-07-27T00:15:08+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/flake8.git/commit/?id=6eca38f2f2a15765aecef010f878aa17fdbe1db7'/>
<id>6eca38f2f2a15765aecef010f878aa17fdbe1db7</id>
<content type='text'>
We accidentally changed column numbering from one-indexed to
zero-indexed.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
We accidentally changed column numbering from one-indexed to
zero-indexed.
</pre>
</div>
</content>
</entry>
<entry>
<title>Add --tee option to split report output stream.</title>
<updated>2016-07-26T13:57:13+00:00</updated>
<author>
<name>Martin Domke</name>
<email>mdomke@jackbird.local</email>
</author>
<published>2016-07-26T13:57:13+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/flake8.git/commit/?id=c782060a0620135b01eb64e15508cca581cb09be'/>
<id>c782060a0620135b01eb64e15508cca581cb09be</id>
<content type='text'>
The --tee option allows the linter report to be written to stdout, even
though it is being redirected to a file with the --output-file option.
This is useful if I want to store the report in a separate file for later
analysis but also be able to print the output on screen (e.g when running
in a CI environment).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The --tee option allows the linter report to be written to stdout, even
though it is being redirected to a file with the --output-file option.
This is useful if I want to store the report in a separate file for later
analysis but also be able to print the output on screen (e.g when running
in a CI environment).
</pre>
</div>
</content>
</entry>
<entry>
<title>Handle repeated --quiet options again</title>
<updated>2016-07-26T00:38:19+00:00</updated>
<author>
<name>Ian Cordasco</name>
<email>graffatcolmingov@gmail.com</email>
</author>
<published>2016-07-26T00:32:42+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/flake8.git/commit/?id=222292c4b2bb595c81d749bfd35ef9adc640bacb'/>
<id>222292c4b2bb595c81d749bfd35ef9adc640bacb</id>
<content type='text'>
Fundamentally on Flake8 2.x using -q altered the format of the errors
(and the behaviour a little) so it makes the most sense to implement
this logic with formatters rather than messy logic spread throughout
the project.

The FilenameOnly formatter will keep track of filenames already reported
and only print the name once while Nothing will print nothing.

Closes #180
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Fundamentally on Flake8 2.x using -q altered the format of the errors
(and the behaviour a little) so it makes the most sense to implement
this logic with formatters rather than messy logic spread throughout
the project.

The FilenameOnly formatter will keep track of filenames already reported
and only print the name once while Nothing will print nothing.

Closes #180
</pre>
</div>
</content>
</entry>
<entry>
<title>Wire-up --statistics again</title>
<updated>2016-07-25T19:29:09+00:00</updated>
<author>
<name>Ian Cordasco</name>
<email>graffatcolmingov@gmail.com</email>
</author>
<published>2016-07-25T19:29:09+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/flake8.git/commit/?id=4dc1d11a627a571eeae4e0ae3da7b94e7de04214'/>
<id>4dc1d11a627a571eeae4e0ae3da7b94e7de04214</id>
<content type='text'>
I'm not sure where this code went or when, but it disappeared. Let's
add it back.

Related #180
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
I'm not sure where this code went or when, but it disappeared. Let's
add it back.

Related #180
</pre>
</div>
</content>
</entry>
<entry>
<title>Handle errors reported in empty files</title>
<updated>2016-07-10T01:21:26+00:00</updated>
<author>
<name>Ian Cordasco</name>
<email>graffatcolmingov@gmail.com</email>
</author>
<published>2016-07-10T01:21:26+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/flake8.git/commit/?id=57e82688df3f36d023352e3d12435f36f51ee9ac'/>
<id>57e82688df3f36d023352e3d12435f36f51ee9ac</id>
<content type='text'>
Some plugins (e.g., flake8-future-import) report errors for empty
files. Those plugins default to reporting the line number as 1 which
caused earlier versions of Flake8 3.0 beta to crash on an IndexError

Closes #157
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Some plugins (e.g., flake8-future-import) report errors for empty
files. Those plugins default to reporting the line number as 1 which
caused earlier versions of Flake8 3.0 beta to crash on an IndexError

Closes #157
</pre>
</div>
</content>
</entry>
<entry>
<title>Move flake8 into src</title>
<updated>2016-06-25T15:12:13+00:00</updated>
<author>
<name>Ian Cordasco</name>
<email>graffatcolmingov@gmail.com</email>
</author>
<published>2016-06-25T15:12:13+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/flake8.git/commit/?id=1a2c68f5da8ae95b8a156ef6f6a772bf82cf0f88'/>
<id>1a2c68f5da8ae95b8a156ef6f6a772bf82cf0f88</id>
<content type='text'>
This is an emerging best practice and there is little reason to not
follow it
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This is an emerging best practice and there is little reason to not
follow it
</pre>
</div>
</content>
</entry>
</feed>
