Pylint pep8 fixes

[jbampton]

No description provided.

[chriddyp]

Thanks @jbampton , you're quick! Do you have these checks automated? I really gotta get #181 merged.

[jbampton]

Hey @chriddyp no I don't have them automated. I just ran Pylint against each file I wanted to check. Also I run Pycharm here and it picks up most of the problems just in the code editor. I mainly just looked at some of the recent commits and noticed some of the PEP8 problems.

[jbampton]

Hey @chriddyp I see the pylint command works on a whole directory at once if you have an __init__.py inside that directory. It should recurse into sub directories that also have __init__.py files. For example on the dash-docs ->
Beast@Destiny~/GitHub/dash-docs $ pylint tutorial

I wanted to catch the Python files in directories that don't have __init__.py so I wrote a Ruby script to automate it as seen below:

#!/usr/bin/env ruby# Ruby command line script that runs the Pylint python code linting tool.# https://www.pylint.org/ against a whole directory recursivelydeflint(src)Dir.glob("#{src}/**/*.py").mapdo |filename|
puts`pylint "#{filename}"`unlessfilename.include?'/venv/'endendifARGV[0].nil?STDOUT.puts'Please provide the directory - /path/to/dir - to run pylint ' \
'against or use . for the current directory.'elselint(ARGV[0])end

Runs like this:

Beast@Destiny~/GitHub/ruby-pylint $ ruby pylint.rb ../dash > dash.txt

I put it up in a repo here -> https://github.com/jbampton/ruby-pylint

[jbampton]

No description provided.

[chriddyp]

Thanks @jbampton , you're quick! Do you have these checks automated? I really gotta get #181 merged.

[jbampton]

Hey @chriddyp no I don't have them automated. I just ran Pylint against each file I wanted to check. Also I run Pycharm here and it picks up most of the problems just in the code editor. I mainly just looked at some of the recent commits and noticed some of the PEP8 problems.

[jbampton]

Hey @chriddyp I see the pylint command works on a whole directory at once if you have an __init__.py inside that directory. It should recurse into sub directories that also have __init__.py files. For example on the dash-docs ->
Beast@Destiny~/GitHub/dash-docs $ pylint tutorial

I wanted to catch the Python files in directories that don't have __init__.py so I wrote a Ruby script to automate it as seen below:

#!/usr/bin/env ruby# Ruby command line script that runs the Pylint python code linting tool.# https://www.pylint.org/ against a whole directory recursivelydeflint(src)Dir.glob("#{src}/**/*.py").mapdo |filename|
puts`pylint "#{filename}"`unlessfilename.include?'/venv/'endendifARGV[0].nil?STDOUT.puts'Please provide the directory - /path/to/dir - to run pylint ' \
'against or use . for the current directory.'elselint(ARGV[0])end

Runs like this:

Beast@Destiny~/GitHub/ruby-pylint $ ruby pylint.rb ../dash > dash.txt

I put it up in a repo here -> https://github.com/jbampton/ruby-pylint

[jbampton]

No description provided.

[chriddyp]

Thanks @jbampton , you're quick! Do you have these checks automated? I really gotta get #181 merged.

[jbampton]

Hey @chriddyp no I don't have them automated. I just ran Pylint against each file I wanted to check. Also I run Pycharm here and it picks up most of the problems just in the code editor. I mainly just looked at some of the recent commits and noticed some of the PEP8 problems.

[jbampton]

Hey @chriddyp I see the pylint command works on a whole directory at once if you have an __init__.py inside that directory. It should recurse into sub directories that also have __init__.py files. For example on the dash-docs ->
Beast@Destiny~/GitHub/dash-docs $ pylint tutorial

I wanted to catch the Python files in directories that don't have __init__.py so I wrote a Ruby script to automate it as seen below:

#!/usr/bin/env ruby# Ruby command line script that runs the Pylint python code linting tool.# https://www.pylint.org/ against a whole directory recursivelydeflint(src)Dir.glob("#{src}/**/*.py").mapdo |filename|
puts`pylint "#{filename}"`unlessfilename.include?'/venv/'endendifARGV[0].nil?STDOUT.puts'Please provide the directory - /path/to/dir - to run pylint ' \
'against or use . for the current directory.'elselint(ARGV[0])end

Runs like this:

Beast@Destiny~/GitHub/ruby-pylint $ ruby pylint.rb ../dash > dash.txt

I put it up in a repo here -> https://github.com/jbampton/ruby-pylint

[jbampton]

No description provided.

[chriddyp]

Thanks @jbampton , you're quick! Do you have these checks automated? I really gotta get #181 merged.

[jbampton]

Hey @chriddyp no I don't have them automated. I just ran Pylint against each file I wanted to check. Also I run Pycharm here and it picks up most of the problems just in the code editor. I mainly just looked at some of the recent commits and noticed some of the PEP8 problems.

[jbampton]

Hey @chriddyp I see the pylint command works on a whole directory at once if you have an __init__.py inside that directory. It should recurse into sub directories that also have __init__.py files. For example on the dash-docs ->
Beast@Destiny~/GitHub/dash-docs $ pylint tutorial

I wanted to catch the Python files in directories that don't have __init__.py so I wrote a Ruby script to automate it as seen below:

#!/usr/bin/env ruby# Ruby command line script that runs the Pylint python code linting tool.# https://www.pylint.org/ against a whole directory recursivelydeflint(src)Dir.glob("#{src}/**/*.py").mapdo |filename|
puts`pylint "#{filename}"`unlessfilename.include?'/venv/'endendifARGV[0].nil?STDOUT.puts'Please provide the directory - /path/to/dir - to run pylint ' \
'against or use . for the current directory.'elselint(ARGV[0])end

Runs like this:

Beast@Destiny~/GitHub/ruby-pylint $ ruby pylint.rb ../dash > dash.txt

I put it up in a repo here -> https://github.com/jbampton/ruby-pylint

[jbampton]

No description provided.

[chriddyp]

Thanks @jbampton , you're quick! Do you have these checks automated? I really gotta get #181 merged.

[jbampton]

Hey @chriddyp no I don't have them automated. I just ran Pylint against each file I wanted to check. Also I run Pycharm here and it picks up most of the problems just in the code editor. I mainly just looked at some of the recent commits and noticed some of the PEP8 problems.

[jbampton]

Hey @chriddyp I see the pylint command works on a whole directory at once if you have an __init__.py inside that directory. It should recurse into sub directories that also have __init__.py files. For example on the dash-docs ->
Beast@Destiny~/GitHub/dash-docs $ pylint tutorial

I wanted to catch the Python files in directories that don't have __init__.py so I wrote a Ruby script to automate it as seen below:

#!/usr/bin/env ruby# Ruby command line script that runs the Pylint python code linting tool.# https://www.pylint.org/ against a whole directory recursivelydeflint(src)Dir.glob("#{src}/**/*.py").mapdo |filename|
puts`pylint "#{filename}"`unlessfilename.include?'/venv/'endendifARGV[0].nil?STDOUT.puts'Please provide the directory - /path/to/dir - to run pylint ' \
'against or use . for the current directory.'elselint(ARGV[0])end

Runs like this:

Beast@Destiny~/GitHub/ruby-pylint $ ruby pylint.rb ../dash > dash.txt

I put it up in a repo here -> https://github.com/jbampton/ruby-pylint

[jbampton]

No description provided.

[chriddyp]

Thanks @jbampton , you're quick! Do you have these checks automated? I really gotta get #181 merged.

[jbampton]

Hey @chriddyp no I don't have them automated. I just ran Pylint against each file I wanted to check. Also I run Pycharm here and it picks up most of the problems just in the code editor. I mainly just looked at some of the recent commits and noticed some of the PEP8 problems.

[jbampton]

Hey @chriddyp I see the pylint command works on a whole directory at once if you have an __init__.py inside that directory. It should recurse into sub directories that also have __init__.py files. For example on the dash-docs ->
Beast@Destiny~/GitHub/dash-docs $ pylint tutorial

I wanted to catch the Python files in directories that don't have __init__.py so I wrote a Ruby script to automate it as seen below:

#!/usr/bin/env ruby# Ruby command line script that runs the Pylint python code linting tool.# https://www.pylint.org/ against a whole directory recursivelydeflint(src)Dir.glob("#{src}/**/*.py").mapdo |filename|
puts`pylint "#{filename}"`unlessfilename.include?'/venv/'endendifARGV[0].nil?STDOUT.puts'Please provide the directory - /path/to/dir - to run pylint ' \
'against or use . for the current directory.'elselint(ARGV[0])end

Runs like this:

Beast@Destiny~/GitHub/ruby-pylint $ ruby pylint.rb ../dash > dash.txt

I put it up in a repo here -> https://github.com/jbampton/ruby-pylint

[jbampton]

No description provided.

[chriddyp]

Thanks @jbampton , you're quick! Do you have these checks automated? I really gotta get #181 merged.

[jbampton]

Hey @chriddyp no I don't have them automated. I just ran Pylint against each file I wanted to check. Also I run Pycharm here and it picks up most of the problems just in the code editor. I mainly just looked at some of the recent commits and noticed some of the PEP8 problems.

[jbampton]

Hey @chriddyp I see the pylint command works on a whole directory at once if you have an __init__.py inside that directory. It should recurse into sub directories that also have __init__.py files. For example on the dash-docs ->
Beast@Destiny~/GitHub/dash-docs $ pylint tutorial

I wanted to catch the Python files in directories that don't have __init__.py so I wrote a Ruby script to automate it as seen below:

#!/usr/bin/env ruby# Ruby command line script that runs the Pylint python code linting tool.# https://www.pylint.org/ against a whole directory recursivelydeflint(src)Dir.glob("#{src}/**/*.py").mapdo |filename|
puts`pylint "#{filename}"`unlessfilename.include?'/venv/'endendifARGV[0].nil?STDOUT.puts'Please provide the directory - /path/to/dir - to run pylint ' \
'against or use . for the current directory.'elselint(ARGV[0])end

Runs like this:

Beast@Destiny~/GitHub/ruby-pylint $ ruby pylint.rb ../dash > dash.txt

I put it up in a repo here -> https://github.com/jbampton/ruby-pylint

[jbampton]

No description provided.

[chriddyp]

Thanks @jbampton , you're quick! Do you have these checks automated? I really gotta get #181 merged.

[jbampton]

Hey @chriddyp no I don't have them automated. I just ran Pylint against each file I wanted to check. Also I run Pycharm here and it picks up most of the problems just in the code editor. I mainly just looked at some of the recent commits and noticed some of the PEP8 problems.

[jbampton]

Hey @chriddyp I see the pylint command works on a whole directory at once if you have an __init__.py inside that directory. It should recurse into sub directories that also have __init__.py files. For example on the dash-docs ->
Beast@Destiny~/GitHub/dash-docs $ pylint tutorial

I wanted to catch the Python files in directories that don't have __init__.py so I wrote a Ruby script to automate it as seen below:

#!/usr/bin/env ruby# Ruby command line script that runs the Pylint python code linting tool.# https://www.pylint.org/ against a whole directory recursivelydeflint(src)Dir.glob("#{src}/**/*.py").mapdo |filename|
puts`pylint "#{filename}"`unlessfilename.include?'/venv/'endendifARGV[0].nil?STDOUT.puts'Please provide the directory - /path/to/dir - to run pylint ' \
'against or use . for the current directory.'elselint(ARGV[0])end

Runs like this:

Beast@Destiny~/GitHub/ruby-pylint $ ruby pylint.rb ../dash > dash.txt

I put it up in a repo here -> https://github.com/jbampton/ruby-pylint