Pin agate<1.6.2 to fix installation #3161
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
kwigley
approved these changes
Mar 12, 2021
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.
resolves #3160
Description
Lots of folks seeing installation errors with the release of
agate>=1.6.2yesterday, since it requiresPyICU, which is not installable viapip(per its most recent installation instructions). Since it is installable via Homebrew, I wonder if we could do something better forbrewinstallations in the long run?In any case, the simplest and surest bet seems to be lowering the upper bound on
agatefrom<2to<1.6.2, sinceagate==1.6.1installs and works just fine.Checklist
CHANGELOG.mdand added information about my change to the "dbt next" section.