will /usr/bin/python then point to python3?
Reason: bluez has test scripts that have a #!/usr/bin/python shebang, but work just fine with python3 (AFAICT).
We also should probably be imposing a policy similar to Fedora and Mageia to force all Python shebangs to be versioned for installed scripts.
(1) Note that the version can be imposed without an absolute path: `#!/usr/bin/env python3` and `#!/usr/bin/env python2`. (2) If absolute paths are used can this be done without encouraging upstream to use such shebangs? Absolute paths make it difficult to run up-to-date software on systems where there is no or too old python[23] in /usr/bin. If `env` is used I can at least help myself with a symlink in a folder early in $PATH (or a wrapper script if I also need to activate an environment first). Joachim -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org