Separate streaming and database streaming. Python 3-ify

[mdeland]

This would be a breaking change since it separates text.streamers from text.database_streamers. The difference is that people can use rosetta.text without having to have database dependencies like pymongo and MySQL-python (the latter of which requires a mysql client dependency, which is kind of annoying to carry around if you aren't using mysql). This would partially address people's install issues (e.g. #48)

The other changes are so that rosetta installs using into python3 environments. There are a couple slightly dirty solutions here, implemented by catching ImportError, but for the most part rosetta is python3 compatible so it might as well work there.

[dkrasner]

this looks good to me; @langmore - thoughts?

it might also make sense to move MySQLStreamer to work with sqlAlchemy, much like pandas.io.sql does; this would solve the compatibility issues with python 3, dependency on mysql from MySQL-python, and could very well be a lot nicer to work with.

[langmore]

Maybe also import

division, and unicode_literals

[langmore]

Thanks for updating things. I like removing the dependencies. If a file split is the only way, then I think it's worth it.

[dkrasner]

yeah i think a file split is the easiest/cleanest; we can also try/except import within the classes themselves (for example: import MySQLdb during MySQLStreamer__init__()) but this is prob easiest, even if it screws up some rosetta import in peoples' code here and there.

@langmore if you are ok with this I'll merge and I think we are due for a release

[langmore]

I'm OK with it.

On Mon, Aug 17, 2015, 4:42 AM dkrasner notifications@github.com wrote:

yeah i think a file split is the easiest/cleanest; we can also try/except
import within the classes themselves (for example: import MySQLdb during
MySQLStreamer__init__()) but this is prob easiest, even if it screws up
some rosetta import in peoples' code here and there.

@langmore https://github.com/langmore if you are ok with this I'll
merge and I think we are due for a release

—
Reply to this email directly or view it on GitHub
#49 (comment)
.