Skip to content

Conversation

@alvinchow86
Copy link

The top-level package name really should be something unique, like segment or segmentio or something. If you have another package or module loaded in your Python load path named analytics, a very common word, there is a name-space collision and it's possible (or very difficult) to resolve in Python. A common case this happens is with Django, if you follow the standard documentation and make an app called analytics that's a top-level import.

# import analytics
import segmentio

This PR renames the module from analytics to segment. I would probably also rename the setuptools name to segment-python or something but left it alone for now.

Related #42

@alvinchow86 alvinchow86 changed the title Package name should NOT be "analytics", rename to segment Rename package name from "analytics" to "segment" Mar 17, 2015
@stevenmiller888
Copy link

cc/ @ivolo @calvinfo ^

@alvinchow86
Copy link
Author

any thoughts or update about this? the top-level package should really be renamed

related issue #42

@diwu1989
Copy link
Contributor

+1 i think it should be named segmentio

@graingert graingert mentioned this pull request Aug 4, 2016
@diwu1989
Copy link
Contributor

it might be even better to just publish a new package completely as segment-python vs analytics-python

@f2prateek
Copy link
Contributor

Closing for #82

@f2prateek f2prateek closed this Nov 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants