sshuttle/run

#!/bin/sh
if python3.5 -V 2>/dev/null; then
	exec python3.5 -m "sshuttle" "$@"
elif python2.7 -V 2>/dev/null; then
	exec python2.7 -m "sshuttle" "$@"
else
	exec python -m "sshuttle" "$@"
fi
Restructure code * Make compatible with setuptools. * Load modules via ssh into separate modules, not the one name space. 2015-11-15 06:45:26 +01:00			`#!/bin/sh`
Try Python3.5 by default. Python 3.0, 3.1, 3.2, and 3.4 not supported however. 2015-12-05 04:40:59 +01:00			`if python3.5 -V 2>/dev/null; then`
Make sure we use Python 3.5 2016-01-30 01:27:37 +01:00			`exec python3.5 -m "sshuttle" "$@"`
If 3.5 not available, try to fallback to 2.7 In situations where 2.7 is available and some unsupported 3.x is the system's default we should probably fallback to 2.7 instead of the default (that might be e.g. 3.4). This might fix #78. 2016-03-13 00:11:20 +01:00			`elif python2.7 -V 2>/dev/null; then`
Don't mix tab and spaces in shell script Sometime ago I was in python mode and incorrectly indented a line of the shell script with spaces instead of tabs. Shame on me. This should bring things back to their natural order. 2016-04-20 02:54:11 +02:00			`exec python2.7 -m "sshuttle" "$@"`
Restructure code * Make compatible with setuptools. * Load modules via ssh into separate modules, not the one name space. 2015-11-15 06:45:26 +01:00			`else`
			`exec python -m "sshuttle" "$@"`
			`fi`