Relaxed rich requirement to allow newer version of it #332
Conversation
This file contains hidden or 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
javiber
force-pushed
the
relax-rich-requirement
branch
from
103f107 to
a8dfd8f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I just relaxeed the rich requirement in the
pyproject.toml. This change affects the resulting package frompoetry buildeven if we don't change thepoetry.lock(I ended up changing the lock because some github actions where failing)Solves #329
Replaces #331. I prefer this change since this version still allows older versions of rich.
This PR ended up being more about fixing the github actions than the actual change we wanted to make.