-
Notifications
You must be signed in to change notification settings - Fork 190
pep257 configuration file #58
Comments
Sure! Pull requests are welcome 😉 |
I'll wait for the merging of your In the mean time, do you have any preferences on the naming and default location ? |
Ini-style config is probably the best choice, since it's supported by standard library. Take a look at this config example. It allows for configs like: [pep257]
--explain
--ignore=D101,D202
--match='(?!test_).*\.py' |
We honor [#]: We == Flake8 |
What do you use if not |
Before having a configuration file, I prefer to have |
btw. I am not using (or plan to use) pep256 directly from the command line. Rather I load a file in memory once and then send the content to many linters and checkers. |
I would like to see |
@kdeldycke are you working on this, or planning to? |
@Nurdok not at all. Feel free to take over this issue ! :) |
👍 any progress on this? |
Not yet, but I consider this the next big thing. On Thu, 11 Dec 2014 12:50 pm Ory Band notifications@github.com wrote:
|
Great. Could youp lease add documentation for this please? Specifically to the front page of this repo (README.md) |
This is a better opportunity to start using readthedocs.org and have real documentation for this project. |
pep8 has
~/.config/pep8
.PyLint has
~/.pylintrc
.Flake8 has
~/.config/flake8
.Even PyChecker had
~/.pycheckrc
.Why can't
pep257
have a configuration file ?The text was updated successfully, but these errors were encountered: