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.
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.