(Re)implement ipex functionality#23432
Draft
HeroCC wants to merge 2 commits into
Draft
Conversation
Contributor
|
@HeroCC If it's not enough, you should at least detail why to prove you've done your homework for future readers. |
This file contains hidden or 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
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.
draft mode. Please don't merge yet - I have some fixes from our plugin to backport to this.
Problem
We are running into the same problem as pex-tool/pex#789. Ie., we have massive pex artifacts (in this case, pyspark) which are slow to upload, and expensive to store (we don't need 100s of copies of embedded pyspark stored at the same time).
Solution
(Re)introducing
ipex- a pex file packaged with sources + a dependencies lockfile. When run, it rehydrates dependencies from whichever requirements file was requested.Essentially the same as #8940
Additional Notes
Ths code here is almost entirely codex w/ GPT-5.5 + some manual tweaks by me. I told it to read the changes from #8940 and reimplement it on top of modern pants, then prompted it to add some more unit test cases we care about (full lockfile resoluton).