tree 75aff99c195968e2d8278807138395d5cfabaf45
parent 759f5da9ade00f60729eff85915bf173597c4767
author Ignas Anikevicius <240938+aignas@users.noreply.github.com> 1765067254 +0900
committer GitHub <noreply@github.com> 1765067254 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJpNMoFCRC1aQ7uu5UhlAAApDEQAFQHRLFTTc7EIOvUkWefVLaw
 /M8mI8HZzn6ofOhjq9/cQI4hemuU0gBKC9bobnUkP0bTGx2q2IifKPhOgVs2BbSJ
 JmNBRFdYi7gxYWEFIVROh+Yjc+iRJPvcqerq7Erd5il0fIBrHC4fgVrTjkbEU9FM
 N/rWqcFEWverJNaLKpWxIBvCM+N7+gnXDZaOwr9SgdMjYqfgQ3a83E8JcmaJbNK8
 9UASGHZz1JrenPUsrvJ8PtUPUgpVNZwkTDKK2l2fR0jEi8555rMXQgYDD/TXCGwg
 nH/gPhy3cZV8Mfl5NX55z0eWaWAy2Xi0eUX84wrS2K9y9ZJcL449B3ZWVd0aVNYz
 pRTUOFfsgj4Zb6/WaMh/rh944kVIl6Yw4B0zpH9d7Joj8mSXi7RWn+NBoErmWbe+
 ofjm0VpYBU/BDyYrxykYveNoNButMFX5bqK8U0YOXvg104cGjGZLabyolKFEI85S
 cjueRNZKDhcAuTXMVHcoi2Lp+i1b3dMi1doW1JlauHoMW9LWxR/Z01KmwSFDPFqk
 6Ug+it0Eau5iiBg+2esnXTwHv4MfGaus58qYMHCjnT4QDNhNF/pJNY21/+kKLLEn
 qMbtUvs+8riprBLg144YQSjmKft5OsqWjT53Fn9w2G2qXF/R7xO0XTelVOD+X8dB
 FlqigMInMIbc8vJ/ki6f
 =AoA9
 -----END PGP SIGNATURE-----
 

feat(pip.parse): limit the target platforms we parse requirements for (#3441)

Up until now the users can configure which requirements files to be used
for specific platforms, however, what they cannot configure is what
target platforms should actually be set up.

The difference in the problems is:
1. I want my `bazel build` to work on `osx aarch64` and `linux x86_64`.
1. I want my `bazel build` to build for `linux x86_64` on `osx aarch64`.

With the newly introduced `target_platforms` attribute users can finally
specify their target platforms. To ensure that this also allows users to
specify that they want to support `freethreaded` and `non-freethreaded`
platforms at the same time we support `{os}` and `{arch}` templating in
the strings.

This should fix the `genquery` usage pattern breakage when we previously
enabled `RULES_PYTHON_ENABLE_PIPSTAR=1`.

Work towards #2949
Work towards #3434

---------

Co-authored-by: Richard Levasseur <richardlev@gmail.com>