-
Notifications
You must be signed in to change notification settings - Fork 17
Appropriate formatting for __init__ file. #544
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
Conversation
hombit
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It works, thanks! Please do not change user's global git settings, even it tests, I believe this type of global changes should happen in CI, not in the test code.
hombit
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
drewoldag
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks fine to me, I believe that it would address the issues that I ran into a few days ago with failing unit tests looking for __version__. Thank you!
Change Description
Closes #542
Closes #538
The initially hydrated
__init__.pyfile was not formatted toruffstandards, and so the initial pre-commit failed when choosing the ruff linting option (the default option).This PR makes an additional change to REALLY run the pre-commits in the unit tests. This catches all the checks that SHOULD be run, given the copier config that the project is hydrated with. The tests take quite a bit longer, but I think it's well worth it to catch such issues in the future.
Checklist
lincc-frameworks/python-project-templaterepo and not a downstream one instead.