no mot namespace will be created
use parentheses for multiple imports
mv version to polytope/version.py

to have a single place where it is defined, while avoiding importing the polytope package when importing the version into setup.py.
After thinking of creating a polytope/__version__.py file, searching led to this discussion: http://stackoverflow.com/questions/458550/standard-way-to-embed-version-into-python-package

Justification for design choices:

- file named version.py instead of __version__.py because __version__ must be a string according to PEP 396

- variable in version.py named version instead of __version__ to avoid creating a __main__.__version__ variable when exec is executed within setup.py

- the exec command avoids loading the polytope package, was borrowed from the discussion linked above. If instead one attempts to use from polytope.version import __version__ in setup.py, the polytope.__init__ will be automatically imported, triggering imports from polytope.polytope, which in turn requires bumpy that may not yet be installed, because all this occurs before setup tools fetch and install dependencies.

- variable version_info seems to be common practice

Drawbacks of the approach: file littering, ugly exec command
Belatedly bump version number

This is in support of the practice of having the version number
in the repository be what it will be upon the next release.  In
particular, the first commit following a release should have the
version number bumped.  In a forthcoming merge, infrastructure for
appending commit hashes to version strings for non-release commits
will be implemented.
Merge branch 'master' into version

Conflicts:
	polytope/__init__.py
	setup.py

The only nontrivial part of this merge is changing occurrences
of the version 0.1.0 with 0.1.1
make ABS_TOL settable from outside pkg
undo last commit
silence optimizer output

The previous flags are not sufficient on new (?) versions of glpk.
Merge branch 'master' into version
Version suffix of -dev-{%H,unknown-commit} for non-release installations

We now use the same method for version labeling here as in the TuLiP
repository, sans some backwards-compatibility stuff required in TuLiP.

The reference commit in the TuLiP repository is
71aefd0659904ccdb8553e5d5f2436933ea42728
DOC: Correct vestigial references to tulip
pass the tolerance value further in intersect
Merge pull request #11 from rmattila/patch-1

silence optimizer output
Merge branch 'master' into overhaul

Conflicts:
	polytope/__init__.py
import matplotlib inline, to avoid delays caused by it

note that the inlined imports are still listed at the top of the file, to respect pep8.
Merge branch 'master' of https://github.com/tulip-control/polytope
Merge branch 'master' into overhaul

The essential conflict was caused by f6a140e4bd9d53868df00ce9d985a13b6c274e3d
which is satisfied by the new implementation of Polytope.intersection, that forwards abs_tol to its callee.

Conflicts:
	polytope/__init__.py
	polytope/plot.py
	polytope/polytope.py