Skip to content

update Pex to 2.77.0#22986

Merged
cburroughs merged 2 commits intopantsbuild:mainfrom
cburroughs:csb/pex-up-2771
Jan 9, 2026
Merged

update Pex to 2.77.0#22986
cburroughs merged 2 commits intopantsbuild:mainfrom
cburroughs:csb/pex-up-2771

Conversation

@cburroughs cburroughs self-assigned this Jan 8, 2026
@cburroughs cburroughs changed the title update Pex to 2.77.1 update Pex to 2.77.0 Jan 8, 2026
@sureshjoshi
Copy link
Member

Supercedes this: #22967

@sureshjoshi
Copy link
Member

Or does it...

@cburroughs cburroughs marked this pull request as ready for review January 8, 2026 21:39
@cburroughs
Copy link
Contributor Author

Or does it...

My hope was that it does, but on my initial quick scan I had hoped that the issue was from lockfile churn but alas! it was not that smooth.

return cast(list[str], get_all_data(rule_runner, pex).info["requirements"])


def _normalize_url_req(s: str) -> str:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As I was alluding to in the other PR, maybe the problem here is with the tests themselves? As in, they're brittle and based on internals that really shouldn't matter?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't disagree: Two lines down:

Several tests here are brittle and rely on Pex/Pants being on the same packaging version

But as a general principle I found patching the assertion the smaller scope creep over delete/refactor a 200(!?) line test.

(I don't think these tests directly matter for this, but I was today looking at areas where we do have inconsistent requirements parsing bugs #22239 which don't give me great "delete the test" vibes.)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I meant deleting the brittle assertions not the whole test itself, then as John wrote in my PR - using the output of the parsed requirements as a comparison point.

I mean, doesn't really matter - but I think there's a pretty small chance this gets deleted eventually 🤷🏽

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah gotcha. I started with that, but once I got to 3 assertions I felt like it was "bigger than a breadbox" or however that joke goes.

Copy link
Member

@sureshjoshi sureshjoshi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other than the idea of just deleting brittle assertions, the update itself is fine.

@cburroughs cburroughs merged commit 3782956 into pantsbuild:main Jan 9, 2026
25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants