Conflicting package name with an already public python package

Hi guys,

I'm just about to start using `hermes` to update some of our metadata but have discovered that someone has released an unrelated package also called `hermes`:

https://pypi.python.org/pypi/hermes/

I'm going to write a `setup.py` script for this and will probably rename the package to `esri-hermes`, but will keep the package folder name as `hermes`, so the distinction will only be to `pip`. We'll put it into our internal PyPi mirror, but it would be nice for this to be published to the public PyPi but I'm not sure what further steps should be taken to avoid the package folder name conflict if someone happened to install both esri-hermes and hermes... Any thoughts?

Review the planned setup.py and the existing hermes package layout first, then check how the distribution name and import package name are handled by PyPI and pip. Done means agreeing on a publication-safe naming and installation approach, including whether both packages could coexist; the issue names no tests or implementation file.

Written by the indexing model from the issue text.