Conflicting package name with an already public python package

[adamkerz]

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?

[adamkerz]

PS. it's a great name! My colleague asked if there was a limbo function or method :-)

[achapkowski]

@adamkerz - I'll look into the PyPi name change, I never actually thought of putting it up there.

[adamkerz]

I've created a setup.py to build the tool and happy to do the folder rename and make sure setup.py builds a package and then send it all as a pull request, just want your input on how to handle the conflict.

My setup.py is here (and a couple of minor changes to separate the version number) and python setup.py bdist_wheel builds a functional .whl file:
https://github.com/adamkerz/hermes

Thanks heaps for putting a little time to it. EVERYTHING we do is in virtualenvs and using python packages (wheels/.whl wherever possible) - that's the way everything is moving.

[achapkowski]

@adamkerz - can you submit a pull request?

[adamkerz]

So if/when we make it uploadable to PyPi, we will need to make sure the classifiers are correct - because I copied setup.py from another project, it still has Python 3 and 3.4 listed, but I doubt this IS python-3 compatible at the moment (need to use relative imports for a start, but probably need a python-3 version of arcpy before that too :)

[achapkowski]

@adamkerz true.