linter for example code about first-analysis-steps HOT 8 OPEN

Argh, I've found linting LHCb software to be extremely tricky because you need the full stack for the linter to recgnize all the Gaudi imports. I am not sure we can make Travis do that, but I agree it would be a nice addition.

What I usually run is pylint and if it passes flake8. This gives properly formatted code (even if I don't agree with some of the formatting rules) but it doesn't bother you about it until the syntax is fixed.

from first-analysis-steps.

Something much more superficial would be pep8 it just checks the formatting of your code (line length, spaces, vertical white space, …)

from first-analysis-steps.

Do you know how to run pep8 on our .md files though? I think pep8
would be more than good enough.

On Sat, May 23, 2015 at 12:11 PM Kevin Dungs [email protected]
wrote:

Something much more superficial would be pep8 it just checks the
formatting of your code (line length, spaces, vertical white space, …)

—
Reply to this email directly or view it on GitHub
#37 (comment)
.

from first-analysis-steps.

My best guess would be that one would have to write a custom pandocfilter for that.

from first-analysis-steps.

With the recent merge of #70, this is resolved now, no?

from first-analysis-steps.

I suppose there's still the ‘issue’ of checking the code that's inline with the lessons. Do you think it's worth checking those?

from first-analysis-steps.

😿
Well... I started working on it and is indeed possible to build something with pandoc that would do this. Maybe keep the idea for later.

from first-analysis-steps.

We could also do it without pandoc using a package like this one: https://www.npmjs.com/package/tests-ex-markdown

from first-analysis-steps.