Skip to content

Conversation

Djailla
Copy link
Collaborator

@Djailla Djailla commented Sep 9, 2025

No description provided.

Copy link
Contributor

@jcuquemelle jcuquemelle left a comment

Choose a reason for hiding this comment

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

This will break client code that still uses this option if cluster-pack is not pinned in all projects using it.

The thing is not about "this is not available by default in PEX", but that this option was mandatory with pex==2.1.137 to workaround pex not being executable if > 2GB.
If you completely remove the support, you need to ensure that all clients pin cluster-pack to the previous version, or update all code that uses this option.

It might be simpler to first relax the constraint on pex to >=1.1.137<2.50 (2.50 has not been tested), release a new version so that you decouple updating all clients and removing the large pex support later

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