Skip to content

pylint documentation doesn't have page listing all command line options #6155

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
gunungpw opened this issue Apr 3, 2022 · 3 comments · Fixed by #6346
Closed

pylint documentation doesn't have page listing all command line options #6155

gunungpw opened this issue Apr 3, 2022 · 3 comments · Fixed by #6346
Labels
Documentation 📗 High effort 🏋 Difficult solution or problem to solve

Comments

@gunungpw
Copy link
Contributor

gunungpw commented Apr 3, 2022

Question

Hello, I am searching command-line options and examples of how to use it for pylint in the documentation but it's very hard and not organized. I want to help document and reorganize commad-line options and maybe config file like pyproject.toml and pylintrc documentation also can get some love :)

Documentation for future user

from my experience, pip docs have good command line section/topic, maybe pylint can copy the way command line options organize in pip

pip commadline docs

Additional context

I love to help, any advice on where I can see all available options and descriptions in the codebase?

@gunungpw gunungpw added the Needs triage 📥 Just created, needs acknowledgment, triage, and proper labelling label Apr 3, 2022
@Pierre-Sassoulas Pierre-Sassoulas added Documentation 📗 High effort 🏋 Difficult solution or problem to solve and removed Needs triage 📥 Just created, needs acknowledgment, triage, and proper labelling labels Apr 3, 2022
@Pierre-Sassoulas
Copy link
Member

Thank you for opening this issue that would be awesome.

Concerning pyproject.toml and pylintrc there's this existing issue : #3181. But this part is under refactoring @DanielNoord is removing the need to have top sections right now. Daniel will probably knows the best way to start documenting this as he's refactoring it currently 😄

For the command line options, there's --help and --long-help. I think it's possible to read it right now and see what isn't clear and need work. If you want to change something you're probably going to need to search for the original string in the whole codebase and modify it because it's integrated in the code.

@DanielNoord
Copy link
Collaborator

@gunungpw I have created #6346 as a first step towards this. I would love feedback on it!

@gunungpw
Copy link
Contributor Author

@DanielNoord Thank you :), i will try to help

@Pierre-Sassoulas Pierre-Sassoulas removed this from the 2.14.0 milestone May 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation 📗 High effort 🏋 Difficult solution or problem to solve
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants