We are finding worrying bugs with Python3

[koolfy]

Recent developments have led us to believe that we might uncover some annoying or dangerous python3 bugss in the future.

The change between python2 and 3 are sometimes somewhat less innocuous than one might believe at first (for example: issue #56)

This calls for a warning message in the README file clearly stating that POTR is experimental and even more so with python3.

In the sort-of-long term, we should us any occasion we get to stress potr with python3 in any way we come up (and write some tests in accordance), to spot all these little pitfalls and fix them litle by little.

For now we haven't found anyhing too critical IMO, but I dont want this to bite someone in the bottom.

[koolfy]

I'm enclined to start dropping python2.7 support to focus on 3+.
This makes it all the more important to triple-check that no weird behaviours will become "the norm" as people make the switch (I'm pretty sure everybody has already done it already...)

I'm thinking travis testing might help here, if someone has experience with pitfalls between 2.7 and 3, now would be a good time to weigh in.
(or shortly, when travis is active for this project)

[koolfy]

It has been pointed out here #47 that python 2.7 support must not be dropped.

[kpcyrd]

What's the status here? python2 is going to get discontinued in a few months and the weechat otr plugin is now using this library with python3 on a recent weechat.