Unpin versions in setup.py (2nd attempt)

This patch unpins versions in setup.py since they are pinned in
requirements.txt. This is effectively a revert of 11c2d9e
and 8fc27f4.

When we originally unpinned versions from setup.py, some clients
were running `setup.py` directly to install `lnt`, which means
they started fetching untested and incompatible versions of
packages.

Since then, we've documented the new installation procedure based
on pip and our pinned requirements (in #70).

Author: ldionne

setup.py

@@ -115,24 +115,21 @@
         ],
     },
     install_requires=[
-        "six",
-        "aniso8601==1.2.0",
-        "Flask==0.12.2",
-        "Flask-RESTful==0.3.4",
-        "Jinja2==2.11.3",
-        "MarkupSafe==1.1.1",
-        "SQLAlchemy==1.3.24",
-        "Werkzeug==0.15.6",
-        "itsdangerous==0.24",
-        "python-gnupg==0.3.7",
-        "pytz==2016.10",
+        "aniso8601",
+        "certifi",
+        "click",
+        "Flask-RESTful",
+        "Flask-WTF",
+        "Flask",
+        "Jinja2",
+        "MarkupSafe",
+        "python-gnupg",
         "pyyaml",
-        "WTForms==2.0.2",
-        "Flask-WTF==0.12",
-        "typing",
-        "click==6.7",
         "requests",
-        "certifi"
+        "SQLAlchemy",
+        "typing",
+        "Werkzeug",
+        "WTForms",
     ],
 
     ext_modules=[cPerf],