Fix pipx workflows #39
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I don't know how the shell line got left off...?
pipx 1.5 breaks relative paths.
changed from daily checks to weekly.
Czarified
added
dependencies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A bunch of silly work to mostly sort out the CI. Lot's of dependencies updated, which broke stuff. After a few hours of googling and migrating things over, this PR has functional CI.
Originally I wanted to support Python 3.12 from the beginning. It seemed to cause issues that weren't immediately obvious, so I'll leave that to a new PR.
Currently, to fix some of the venv stuff, I force pipx==1.4.3 instead of the latest 1.5.0. A fix to absolute path reference for the constraints.txt should allow 1.5.0.
Safety is failing. I expect these dependencies to be updated in the future via dependabot PR's, and resolve that. Right now, the security risks aren't a problem because there's no one using this library.