Some ideas for skimage
Johannes Schönberger
jschoenberger at demuc.de
Fri May 17 04:05:07 EDT 2013
+1 on including it as a build report, but please at the end of the build process.
In case we agree to add this feature, it's probably best if I include it as part of this PR: https://github.com/scikit-image/scikit-image/pull/538 … this actually shouldn't be more than 2 extra lines… any preferences regarding the style guide checker (pep8.py, pyflakes, …)?
Johannes Schönberger
Am 17.05.2013 um 09:53 schrieb Ankit Agrawal <aaaagrawal at gmail.com>:
> @Josh : I agree that most of PEP8 tests are flexible in order to give priority to readability. Perhaps, I was thinking to have tests for style-guidelines that are rigid, for eg : trailing whitespaces, spaces around '/', '*' etc, file ending with a newline etc.
>
> How about only including it as part of the Travis build report (but
> not failing)?
>
> @Stefan : This seems a good middle way.
>
>
> --
> You received this message because you are subscribed to the Google Groups "scikit-image" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to scikit-image+unsubscribe at googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
More information about the scikit-image
mailing list