pip cache always uses node process architecture, ignoring architecture key

[alex]

Description:

The pip caching code uses a cache key that does not include the Python binary's architecture. This leads to cache thrashing.

https://github.com/actions/setup-python/blob/main/src/cache-distributions/pip-cache.ts#L68-L75

These keys should include the Python binary architecture, which is specified with the architecture input to the action.

Action version:
5.2.0

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Tools version:
All

[priya-kinthali]

Hello @alex 👋,
Thank you for this feature request. We will investigate it and get back to you as soon as we have some feedback.

[aparnajyothi-y]

Hello @alex , This change, introduced in PR #896, adds the architecture to the pip cache key. This approach enhances caching efficiency by preventing cache thrashing when switching between different Python architectures (e.g., x86_64 and arm64). As a result, builds become faster, and multi-architecture workflows are better supported.

Please validate this from your end and share any further inputs to confirm the exact requirement.

[alex]

No, that PR does not address this issue. If you look, you will also see that that PR was merged before I filed this.

That PR makes use of the node processes' architecture. But what I requested is the Python binary architecture.

On Windows, these can differ. On Windows, both x86 (32-bit) and x86-64 (64-bit) Python binaries can be installed, and the node process architecture will always be 64-bit.

We need to include the Python binary's architecture, which is specified with the architecture key to the setup-python action.