Believe me, I did consider it. It'd have made things easier a bit. But the goal (as stated in Github) is to not depend on any external module. Execution flow should be to wget && python varnishtuner.py similar to the way mysqltuner.pl works.
Just a suggestion. If you want a single file - why not package everything as an egg? Something that remotely resembles static linking in compiled languages.
I mean, as a part of build process[1] create a ZIP file, containinng all the dependencies and a file called `__main__.py`. Name that file `varnishturner.egg`, and just `python varnishturner.egg` would do the trick.
Or you can ignore this arcane approach suggestion and just publish on PyPI. I suppose Python installations without pip (or at least easy_install) are rare sights.
___
[1] Custom `Makefile`s to the rescue, or there's `bdist_egg` in distutils, although you'd have to write dependency packaging logic by yourself. For example, you can check how lxml does this with their `STATICDEPS=True python setup.py bdist_egg` process.
