Merge lp:~exarkun/game/network-client-virtualenv-friendly into lp:game

[Jean-Paul Calderone]

This updates the client executable to be virtualenv-friendly (by looking up python in the environment instead of hard-coding /usr/bin/python).

I opted not to take this a step further and replace the script with a setuptools command line entrypoint because when I've worked with those elsewhere they've been rather annoying during develop against, since they require you install the package *and* they often require you to re-install the package any time the version changes (even if the command line entrypoint hasn't changed) - failing with a dumb exception when you forget to do this.

Unmerged revisions

51. By Jean-Paul Calderone on 2014-10-19

Use /usr/bin/env to find python in the PATH.

This is preferred over hardcoding the typical location of /usr/bin/python because
it means the correct interpreter will be found when the script is installed in a
virtualenv (meaning the script will operate correctly in a virtualenv, whereas
previously it would not).

=== modified file 'bin/network-client'
--- bin/network-client	2011-01-28 04:13:59 +0000
+++ bin/network-client	2014-10-19 19:58:24 +0000
@@ -1,4 +1,4 @@
-#!/usr/bin/python
+#!/usr/bin/env python
 import sys
 from game.scripts.network_client import NetworkClient