Make the structure more testable

[ibiBgOR]

I would love to see the project more structured so it could be better tested (i know: nobody likes to write tests, but they are extremly helpful whenever i had rewritten the convert function selection)

http://docs.python-guide.org/en/latest/writing/structure/
^^^ Could be one possibility to structure the project ^^^

[kalkehcoisa]

I'm sending a pull request with some structural changes in the project.
I would recommend turning the converters into classes to make the code simpler to deal for developers improving it and for people using it as well. ;)

That's all for today, if you want I can start doing it later and starting making tests.

Oh! I would recommend making the project only for python3. People are - finally - migrating to it \o/
And maintaining a dual version project makes things far more complicated, slower and harder.

Well. That's it. ;)

[mattgd]

Thanks, @kalkehcoisa!

People are definitely starting to migrate now. After a bit of thought, considering there's probably very few people making use of this project yet, it probably would be fine to refactor things to make it Python3 compatible only.

If anyone else has an opinion on this issue, please let us know.

[kalkehcoisa]

@mattgd No problem! ;)
Yeah! I'm gonna try to keep it compatible with both and make python3 only when things become complicated to maintain.