Generalizing, how is SUSE handling all upstream projects that have
"#!/usr/bin/env python"? Are you patching all of those to
#!/usr/bin/python3 ?
Please don't....
Sorry, I think I miswrote my previous response.
"#!/usr/bin/env python" fails when there is no "python" symlink in the
system (which is the case in at least Fedora and openSUSE when Python 2
is not present). So what I'm proposing here is to change
#!/usr/bin/env python
to
#!/usr/bin/env python3
Willem, is that a problem for you?
In a more extreem extend I would even suggest as much as writing a
python selector of a kind so the shebang would be like:
#/usr/bin/env python-version-select
And then set an ENV like: PYTHON_VER_REQ=3 or something of the kind.
Or any other preferred why of selecting the choice of day.
I'd rather be explicit and write python3. Then there's no doubt what is
required. Python 3 is not a "choice of the day". It's the emerging
standard that will be around for years to come.
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
