In its current state, sphinxtrain has inconsistencies in the shebangs used for Python files. 30 of the files use #!/usr/bin/env python while 5 use #!/usr/bin/python. At least one of those files cause issues both on macOS and Debian/Alpine. On macOS, the sphinxtrain executable fails because it cannot find the Python executable (zsh: /usr/local/bin/sphinxtrain: bad interpreter: /usr/bin/python: no such file or directory ) wheras on Debian/Alpine the sphinxtrain command can't even be found because of this. With the changes in this PR, sphinxtrain can be found/executed on the Linux distros and on macOS.
In its current state,
sphinxtrainhas inconsistencies in the shebangs used for Python files. 30 of the files use#!/usr/bin/env pythonwhile 5 use#!/usr/bin/python. At least one of those files cause issues both on macOS and Debian/Alpine. On macOS, thesphinxtrainexecutable fails because it cannot find the Python executable (zsh: /usr/local/bin/sphinxtrain: bad interpreter: /usr/bin/python: no such file or directory) wheras on Debian/Alpine thesphinxtraincommand can't even be found because of this. With the changes in this PR,sphinxtraincan be found/executed on the Linux distros and on macOS.