-
Notifications
You must be signed in to change notification settings - Fork 30
Use the referencing library where available
#253
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
689d45e to
7c68e35
Compare
|
So many distinct changes squashed into a single PR :( |
Well, I couldn't run pre-commit without it and didn't want to make workarounds. |
|
Context for the autopep8 is that the previous hook repo was unmaintained and stopped being updated (doesn't work at all on py3.13). Replaced it with what was recommended as replacement and with |
eeb39f5 to
9388990
Compare
|
And of course I have a typo in commit message refferencing -> referencing. |
Let's address at least the |
9388990 to
96721d4
Compare
96721d4 to
89cd184
Compare
psss
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.
Thanks for looking into this! Looks good, just a few minor comments.
referencing library where available
|
/packit build |
Use the
referencinglibrary where available instead of deprecatedjsonschema.RefResolver.Addressing #194 .
Getting rid of deprecation warnings.