GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||||
GeezerVison is showing github.com — fix: Fix numpy version specification by acmarco · Pull Request #3241 · feast-dev/feast ConversationWhat this PR does / why we need it: The install script for version 0.22 creates conflicts with other packages over the version of numpy. It looks like the version specification is wrong as it is unusual to see redundant constraints like what is there now (i.e: <1.22 and also <2). Which issue(s) this PR fixes: Fixes #
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
Member
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
|
There was an error while loading. Please reload this page.
My commit is signed (i.e: "This commit was signed with the committer’s verified signature. ") ... but maybe you mean another type of signature? Sorry if I am misunderstanding, @achals |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
hey @acmarco, thanks for the PR! here's what we mean by signing your commits also, is there a particular reason you're using Feast 0.22 instead of Feast 0.24? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Signed-off-by: Marco Gagliano <[email protected]>
92f2c06 to
73b33da
Compare
Ah! OK. Sorry for the confusion. signed off. The reason we are stuck on 0.22 is not Feast related, but that we install feast in same python env as other packages that require older versions of numpy and pandas. Upgrading other packages or re-jigging our envs would unblock upgrading Feast, but is a bit complicated right now. Definitely on our roadmap to upgrade Feast and the other packages we use. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@acmarco got it, that makes sense. I'll approve this PR and cut a patch release (0.22.5) once it's in! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: acmarco, felixwang9817 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
thanks for taking the time to address this PR. I was just wondering when the 0.22.5 patch might become available. thanks! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Let me cherrypick this right now and release! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
## [0.22.5](v0.22.4...v0.22.5) (2022-10-28) ### Bug Fixes * Fix numpy version specification ([#3241](#3241)) ([298bdde](298bdde))
|
Actually this PR doesn't make sense for specifically 0.22. We dropped Python 3.7 support in 0.23 (numpy 1.22 also drops this), so this results in a failed release. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, i don't follow, but I just want to confirm that a it will not be possible to publish a 0.22.5 patch release with the changes from this PR. If not, is there any easy way to remedy that on my end? If there is no way, I'll consider this matter closed. thanks |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Yeah it will not be feasible. It's feasible to cherry-pick this into any minor release afterwards (i.e. 0.23+) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.