CI: chain requirements to ensure compatibility #3112
Conversation
|
@Borda thanks! I guess let's wait for all checks to be green before coming back to this |
Borda
force-pushed
the
ci/requirements
branch
from
5717472 to
bf3e0e9
Compare
@lostella done; just curious why rebasing and not just merging the |
whatever works :-) what I meant is to update the branch so that CI workflows run |
|
If possible, I would suggest dropping |
|
we can also move the pytorch version to 2.x no? |
probably but lets make it as separate PR 🐔 |
Yeah we should get rid of that |
lostella
changed the title
*Issue #, if available:* atm, all install requirements are installed as stand-alone, which means if there is a version collision, `pip` does not care about it, and so for eventual version compatibility, a collision may not be discovered *Description of changes:* just install all needed requirements for the particular job at once so pip sees all required packages and finds an intersection among all :flags: By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice. cc: @jaheba @kashif @lostella kind ling as it seems there are no revivers by default 🐿️ **Please tag this pr with at least one of these labels to make our release process faster:** BREAKING, new feature, bug fix, other change, dev setup
Issue #, if available: atm, all install requirements are installed as stand-alone, which means if there is a version collision,
pipdoes not care about it, and so for eventual version compatibility, a collision may not be discoveredDescription of changes:
just install all needed requirements for the particular job at once so pip sees all required packages and finds an intersection among all 🎏
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
cc: @jaheba @kashif @lostella kind ling as it seems there are no revivers by default 🐿️
Please tag this pr with at least one of these labels to make our release process faster: BREAKING, new feature, bug fix, other change, dev setup