Skip to content
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

Include pylintrc and pytest.ini files for each exercise #3690

Closed
rzuckerm opened this issue May 4, 2024 · 1 comment
Closed

Include pylintrc and pytest.ini files for each exercise #3690

rzuckerm opened this issue May 4, 2024 · 1 comment

Comments

@rzuckerm
Copy link

rzuckerm commented May 4, 2024

It would be nice if I could lint my code locally with the same pylint configuration file as the server uses. I was quite surprised the first time I submitted a solution, and the server reported several linting errors.

Also, please include the pytest.ini file. I don't like seeing warning when I run the tests locally. I discovered what I needed to do to suppress that error, and now I have to copy that file over for every project I do. I know there is #2745 .

I'm willing to do the work on this, but someone will need to point me in the right direction as to what I need to change.

Copy link
Contributor

github-actions bot commented May 4, 2024

Hello. Thanks for opening an issue on Exercism 🙂

At Exercism we use our Community Forum, not GitHub issues, as the primary place for discussion. That allows maintainers and contributors from across Exercism's ecosystem to discuss your problems/ideas/suggestions without them having to subscribe to hundreds of repositories.

This issue will be automatically closed. Please use this link to copy your GitHub Issue into a new topic on the forum, where we look forward to chatting with you!

If you're interested in learning more about this auto-responder, please read this blog post.

@github-actions github-actions bot closed this as completed May 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant