Hi all,

Not so much of a bug but a general suggestion/call for feedback. Since gnome-tweak-tool is fairly important DE software, I wanted to run the idea by you of forcing its interpreter to be /usr/bin/python as opposed to the python instance found by /usr/bin/env. I tend to like to try out different Python interpreters and do not always do this within a virtualenv. I imagine that others might do the same and also prefer their default Python in their path to be a different, newer Python interpreter as opposed to the one intended to be their system default.

Since the system-default /usr/bin/python(2) is standardized by https://www.python.org/dev/peps/pep-0394/, and there seems to be little to gain by using the env lookup, but there are cases where using env lookup would cause the gnome-tweak-tool to fail, does switching to the hardcoded interpeter make sense to you?

Let me know what you think, and thank you for maintaining such a useful tool.

-Tom