Suggestion: rename this repository to api-python

[yurishkuro]

but keep the package name as opentracing

[yurishkuro]

@bensigelman @adriancole @slimsag you ok with renaming to api-python?

[codefromthecrypt]

yep, prefer opentracing-api-python* but fine with api-python

• dealing with users, I've found many git clone into a shared directory and that explaining how to rename to something less likely to clash isn't that great use of time.

[yurishkuro]

ha, this is what I have it called locally. I'm fine with opentracing-api-python. I think Go version is the only one that's actually sensitive to the exact repo name, since in Go the import with such name would look like

import "github.com/opentracing/opentracing-api-go/opentracing"

[codefromthecrypt]

yeah that looks like hell. good point.

[bhs]

I'll rename it api-python... the original name was just a side-effect of the fact that I couldn't push my rename branch to Uber so I hastily cloned the repo without thinking about the naming inconsistency!

[codefromthecrypt]

+1 api-python

[yurishkuro]

I updated the .io site to match

[bhs]

Excellent!