Closed MaxGaukler closed 4 years ago
Hi Max,
This is a good idea. Do you have any cycles to work together on this? We could make it its own project separate from Hyst.
Hi Stan,
I'm not sure if detaching hypy from hyst is helpful or not, but I would be happy either way.
I probably won't have the time to do the whole Python3 conversion on my own, but would be happy to cooperate.
Suggested steps:
My goal would be to have most of these done by the end of the year, so I can drop python2 from other code. What's your timeline?
Honestly, I'll start to have some cycles in December, so that's when I would suggest we do most of the work. I wouldn't mind rewriting some of the subprocess code, as if I remember correctly python 3's interface was better than python 2. The idea to include test metrics is good.
Starting in December sounds good - let me know then, so we can work together.
Hypy currently only supports Python2, which is no longer maintained after the end of the year. Many packages are also dropping Python2 support (see https://python3statement.org/ ), or have already done so, so it is difficult to write code which combines Hypy and other packages.
Therefore it would be great to make Hypy compatible with Python3. As it's possible to make code compatible with both Python2 and Python3 (see https://python-future.org/ ), that would probably be the best way to go.