Remove IPEX (Intel Extension for Pytorch) support.#13653
Remove IPEX (Intel Extension for Pytorch) support.#13653comfyanonymous merged 1 commit intoComfy-Org:masterfrom
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughThis change removes Intel Extension for PyTorch (IPEX) integration from the codebase. The 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.Comment |
Intel Extension for Pytorch (IPEX) was an early downstream fork of Pytorch by Intel to add XPU or Intel Arc support to the project. They started in 2020 and releases had came out all the way up to Pytorch 2.8.0 in August of 2025. And then the team announced in intel/intel-extension-for-pytorch#867 in October shortly that they would be discontinuing it in favor of upstreaming support to Pytorch itself. And indeed, today, since #6069, that has been the first recommendation for any Intel GPU users. Since #10729, the instructions for IPEX installation has been removed from the README.md and given that the repository for IPEX has been archived since March 30th, I think it's about time to remove it even though the Pytorch versions it covers are technically still supported by ComfyUI since there is no upstream support now for those Pytorch versions themselves.
Not sure if this needs some sort of process to pass since this is somewhat of a pretty big change to do on one backend but I do believe because of the above reasons I mentioned, it is appropriate. Please let me know if there is anything I would need to do or change to get this through. Also, want to tag @qiacheng to get some input and feedback about this issue.