Widen dependencies
See original GitHub issueIs your feature request related to a problem? Please describe.
Feast often needs to be installed alongside other libraries. Currently Feast pins many of its dependencies to the minor version instead of using a broader range. This means that if other libraries also pin to narrow version ranges, dependencies just can’t be resolved.
Describe the solution you’d like
Change setup.py
to use wider ranges for various dependencies. I’m not sure how that changes your testing strategy. Do you have to do some amount of matrix testing for important dependencies?
Describe alternatives you’ve considered
Not sure.
Additional context
N/A
Issue Analytics
- State:
- Created a year ago
- Comments:7
Top Results From Across the Web
What are dependent metadata fields? - Widen Connect
A dependent metadata field is a field that's tied to another metadata field. When one parent field is completed, the dependent child field...
Read more >8.10.2.5. Expand Dependency to Component Level
Expand Dependency to Component Level. The Exploration view offers the possibility of showing dependencies between all kinds of elements of the parser model, ......
Read more >germinate — expand dependencies in a list of seed packages
It takes a list of seed packages and a mirror of the distribution, and produces outputs with the seed packages and their dependencies...
Read more >Dependencies - Learning UML [Book] - O'Reilly
An extend dependency is responsible for defining when an extension use case is inserted into the base use case by specifying a condition...
Read more >Declaring dependencies - Gradle User Manual
Every dependency declared for a Gradle project applies to a specific scope. ... A configuration can extend other configurations to form an inheritance ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We had a quick discussion. Seems like the preference is to throw errors if we see timezone naive timestamps and only use the
TIMESTAMP
We can make this nicer in the future too with data source validation during
feast apply
@chhabrakadabra I see thanks for clarifying.