Re: [PATCH] python: prioritize python 3.x over 2.x
Mike Frysinger <[email protected]>
| Newsgroups | gmane.comp.sysutils.automake.patches |
|---|---|
| Message-ID | <YfINhj2Tg6Hh6NtF@vapier> |
On 26 Jan 2022 10:11, Zack Weinberg wrote: > On Wed, Jan 26, 2022, at 10:07 AM, Zack Weinberg wrote: > > On Wed, Jan 26, 2022, at 6:37 AM, Mike Frysinger wrote: > >> Since Python 2.x went EOL years ago, stop searching for it before > >> any of the Python 3 versions. > > > > +1 > > It occurred to me right after pushing "send" that this is a potentially breaking change, for anyone who hasn't bothered to update their code to Python 3 yet and is relying on AM_PATH_PYTHON's search order to prefer Python 2. I'm still in favor of the change, but I think it should get a NEWS entry. they're already broken. `python` has never been guaranteed to be Python 2, and many distros & site admins have changed it to be Python 3. def worth mentioning in the NEWS. -mike
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEuQK1JxMl+JKsJRrUQWM7n+g39YEFAmHyDYYACgkQQWM7n+g3 9YF6cBAAmv27u622nJw8xGdVN0+3CVl3MRZAS0W79EqJ1+R33kI3Mg1NuJf7eCmr hxpzRZJjYEANDVZL556ZeTWs6j5xhmRfzYCuSWLiywc0D1T0NhCLiecFQvXqwS93 Ho89EW9UKyym8ijMdZ/XfcGmJRTIyQCxmduYJsiupllX5q74wDoQP2bhj6o6iv/B euZFg1XehijES49Zz4ZGjZfhZ6jFl2X5UL4prvGzVyxcgtHj9Jt+NsefD+l+WFEL Z6bXi9L5lzI54OMMMElR3CacooD2fuQtDR9emNDRknvmJ6Jrkq/97gUUfgCOEmdB JtAj5/Cf3zwTWZqToKjDdc49Y3KhfTB+sex/mJqr9sOsC1E3cGXjx/mNtHHEI4MA bDVY0VENrpvY2weB2XJAEL68OjIgTtbFnXe/0XkeyTgZsaEic9dNc+0ypz2FkLZj alpe2nmQ1Rej6c+zW7u6Iyi0hMVmamdi9Qw0f/7XIxY+nMxZsD0FKNqhbkeXhvtX 1ZHrIAuYKz1BHq+Vwb5Q66l+Ri3YpK4EvLJUBMwiP1fZqoBud4/zt7Q4t9nb7Q/F 0UHgfG4JBh03olW2Pzos5xjY6dWsMEHieL4iXM6lud1xUhwKccVcgkVjPlwMjBng 0bhEOnPvKGE4Bqhdv3USr1ssezFng9qEEIQu5O0teN4D6Jj1b3o= =MalX -----END PGP SIGNATURE-----