On 20-02-2018 10:20, Nathan Cutler wrote:
Work is now ongoing to gradually wean Ceph off Python 2.
[...]
In my mind, the "right" solution is to change "#!/usr/bin/env python" to
"#!/usr/bin/env python3" and fix whatever Python 3-related breakage
might ensue. That, of course, assumes that we have collectively reached
a point where we're ready to declare Python 3 a hard requirement for
"make check".
Any objections to that? Alternative solutions to this dilemma?
If we are replacing "python" for "python3" in bash scripts, and say that
python2 is optional, how do we run "make check" in a python2 environment?
Nathan
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Ricardo Dias
Senior Software Engineer - Storage Team
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284
(AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
