-
Notifications
You must be signed in to change notification settings - Fork 13
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
Setup pre-commit with useful plugins #85
Conversation
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.
The new pre-commit check fails.
What was the inspiration for this?
I've always wanted to play around with pre-commit and black but have always been hesitant because I haven't gone through the trouble of making sure black doesn't royally screw up git blame. If we address that and make sure that we still support Python 3.6, I could be open to this. |
Oh and I missed that you're using the
|
@brianhlin - you want https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view . And yes, precommit tries to bump you to their CI. I tend to just ignore that. |
If you're interested in going with these tools, some automation to keep folks in sync is usually helpful. |
We can't use it if it fails the check. Do you plan to fix it? The tools in this package are quite small and hardly seem worth spending much effort on. |
Fixing the check is trivial; I can get that done if this is a direction folks are interested in. |
I think that as long as you've done the work we might as well include it. It sounds like the Brians are in favor too. |
float_to_top = "True" Might need to be removed because of I'd be tempted to use |
@jcpunk can you add a |
What do you mean? What type of way of calling them would be tripped up by
How does that help? |
It looks like the scripts are expecting to adjust The setuptools console_scripts will generate these |
Added the ignore revs file |
@jcpunk it looks like those Python path hacks are just that, hacks to make unit testing happy and to make life easier when running in a virtualenv. I would definitely like both to continue working so if you've got alternate suggestions for those use cases, I'm all ears! |
I think my current PR should leave them in place.
…On Fri, Mar 29, 2024, 4:26 PM Brian Lin ***@***.***> wrote:
@jcpunk <https://github.com/jcpunk> it looks like those Python path hacks
are just that, hacks to make unit testing happy and to make life easier
when running in a virtualenv. I would definitely like both to continue
working so if you've got alternate suggestions for those use cases, I'm all
ears!
—
Reply to this email directly, view it on GitHub
<#85 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA2673SAWYIDC7D73U2QANDY2XMCBAVCNFSM6AAAAABFD5X646VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRXG42TCOJWGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
In that case, I'm happy with this unless @DrDaveD has any other thoughts |
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.
Looks OK to me
This adds support for pre-commit to the repo which can greatly simplify consistent code practices.