tree 3c6b1674cbab15a612b0c2c67fe7b89c088dffc4
parent bd65eedaa6af5e87206501e468daa830fd0ca20e
author Alexey Preobrazhenskiy <preobr@uber.com> 1705387608 +0100
committer GitHub <noreply@github.com> 1705387608 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlpiZnCRBK7hj4Ov3rIwAAp0sIABhpuOyTd0y88N6r5duUq680
 s0xNeUAQC0cW6vWyiFTv5bdrfBHzcDMQ/NJnl5qkerItezNRXiEsepgIXnG5K4Ci
 ST1D3Iu5yHJE3uOWr2XJ7oVX2WmUx3ABk6vHZqm/O+yaVIqtyJwHB+2pc+SBGFxF
 NmgWp3tHsb8ia7H/h+fqJg32OWQE50zulForkPgPWDNt7yfg8OXgmakBfOTBFxAZ
 Dkj+p2RlO1HkE2QRFOGrafXiBJ0sJHt61Wer8ygjl8l/ClyOcWINg1L7oOQ9BFpw
 Q2xnuJjAqYMon0mUq550HAUCLE3+9riXmNoYNhfYjSbfXuw2k+fdginTdGupSeI=
 =jIpD
 -----END PGP SIGNATURE-----
 

feat(config_settings): allow matching minor version of python_version flag (#1555)

Currently a user has to specify a full (x.y.z) version of Python when
setting the `//python/config_settings:python_version` flag. When they
upgrade `rules_python` or change `MINOR_MAPPING` in some other way, user
has to update the flag's value to keep it in sync with `MINOR_MAPPING`.

This adds micro-version agnostic config settings to allow matching the
minor version.
For example e.g. `//python/config_settings:is_python_3.8` will match any
of
`3.8.1, 3.8.2, ...' (or whatever other versions are listed in
`TOOL_VERSIONS`)

---------

Co-authored-by: Richard Levasseur <rlevasseur@google.com>