Update the requirements.txt file
#100
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
griffin-h
reviewed
Jun 4, 2024
There was a problem hiding this comment.
I don't think we want to downgrade tomtoolkit or tom_swift, because we use features from the latest versions of both of those. Instead, I fixed the dependency conflict in TOMToolkit/tom_nonlocalizedevents#37 and switched that requirement to my personal branch (until that PR is merged). Try installing now and see if you can get a consistent environment.
|
This fixed it on my end! Thanks, this is a much better solution! |
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 lot of the requirements were broken, there were a lot of conflicts. Some of the notable changes that may break things:
I had to do this because of this known issue with the tom-nonlocalizedevents package that makes it incompatible with the current tomtoolkit version.
This is discussed briefly in Issue #99 and unfortunately the only solution I found is downgrading the tom-swift package to an alpha version. This is obviously not ideal but I think it works for now until they fix the issue with the tom-nonlocalizedevents package.