[19757] in Kerberos_V5_Development
Re: Python 3 for k5test.py
daemon@ATHENA.MIT.EDU (Robbie Harwood)
Mon Apr 30 12:10:40 2018
From: Robbie Harwood <rharwood@redhat.com>
To: Greg Hudson <ghudson@mit.edu>, krbdev@mit.edu
In-Reply-To: <x7dbme3p1ab.fsf@equal-rites.mit.edu>
Date: Mon, 30 Apr 2018 12:04:56 -0400
Message-ID: <jlgfu3cof2v.fsf@redhat.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5045375754485564325=="
Errors-To: krbdev-bounces@mit.edu
--===============5045375754485564325==
Content-Type: multipart/signed; boundary="=-=-=";
micalg=pgp-sha512; protocol="application/pgp-signature"
--=-=-=
Content-Type: text/plain
Greg Hudson <ghudson@mit.edu> writes:
> I am thinking now might be the right time to move to Python 2 to
> Python 3 for the Python test suite. This is based on:
>
> * Per https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes, Ubuntu 18.04
> doesn't install Python 2 by default, and implies that 20.04 won't
> include Python 2 in main. (I would guess it might continue to be
> available in universe.)
>
> * https://fedoraproject.org/wiki/FinalizingFedoraSwitchtoPython3
> anticipates an update to PEP 394 recommending that /usr/bin/python be
> Python 3, and talks about maybe getting rid of Python 2 in a few
> years.
>
> Right now the test suite requires Python 2.5, which was released
> roughly three years before Python 3.0. My thought is that if someone
> is building MIT krb5 on a system too old to offer Python 3, they are
> probably building multiple newer versions of software packages, and
> adding Python 3 to that set isn't a huge burden. Or they can just not
> run the test suite. But if someone has a need to build and modify
> krb5 1.17 on a post-2020 operating system which doesn't conveniently
> offer Python 2, having to build Python 2 just for our test suite could
> be more of a burden. Of course that might also happen for 1.16 and
> prior, but we can't reasonably do anything about that.
>
> I prototyped the work required back in February, and it isn't a lot:
> https://github.com/greghudson/krb5/commits/python3
>
> If we don't make this change now, I will at least make configure.in
> look for "python2" in the path in preference to "python", and to skip
> the Python tests if the interpreter we do find has sys.hexversion >=
> 0x3000000.
I would appreciate this. Fedora already generates warnings [1] for
assuming /usr/bin/python is python2 in shebangs (they want explicit
/usr/bin/python2 or /usr/bin/python2), and currently is planning to drop
python2 at or before 2020 as far as I know.
Thanks,
--Robbie
1: https://taskotron.fedoraproject.org/artifacts/all/83108d26-47f0-11e8-afb2-525400fc9f92/tests.yml/output.log
--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEA5qc6hnelQjDaHWqJTL5F2qVpEIFAlrnPqgACgkQJTL5F2qV
pELftBAAl5JZ0or14R6aTkvPpfK29RM1jeb1KZ+Gzqwy6lrIunslwqG9oX5NJ7Do
ANM7QqP4bXTiH1txsLfacGkUTOGk7+uDyCi5dPzuRM2nKmjp6MXdSlllE5AF5iSZ
WmjGfEXrjSxKpJSWuKz4UXdS8xlg8B+GsJbYgPPLV7s0sh/VfFb3RjeyfFfMGL6d
4Z54D3DyZ+MHWkD1nimyj7MgNLRKZos+kvC8APJDofk7Gak+3m9r/yB3WGUgLDz5
LXoCJ5AGgz9KZI+UYGiz8ZX/kYjKw70hQ0hIcansHMmszWgDHottEhgasOuvCdZu
y4HgXeyMMup7/nS+kJ2VkwAhYG/nBG+mRpZjfLeQSkcInYj23VIWoER5GEXpOvYL
U1WiKltgM9soy3pFsIrhaidwx4uRWUSeY3LlFc3a985gB/BNGkIS9VvcPSGR/eAO
H7yM3zgW7kO9TLgcBaayGwnZ6cPWS+1pZOhiiRkt1Dm+WvGdaKcVD6fLWD5AMwJg
chAhtgNnHg1z8LLcqPjHAHX3yMr+6QS4n9wV/A7JtNLqDM/+z0VWxdo8N0AB34kF
qiopn79ql6bXOaKcUmzcFZTwJzg31WHMiCB34gG6iuk/TwWS2wfPTnT/MtwlrYUB
oKluU8S8AUq54SCasEi/AFe1DMpXc/6KIFqE9k83ENgiGZtblN0=
=IrVr
-----END PGP SIGNATURE-----
--=-=-=--
--===============5045375754485564325==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
--===============5045375754485564325==--
