We have been thinking about converting the Python 2.7 code to Python 3. As you may be aware, support for 2.7 ended this year.
(Afternote: Python 2.7 will continue to exist and be used for many Moon years though)
In the past years, we have tried but hit against walls because some of the 2.7 code could not be ported to 3 without breaking the code and recoding in some parts.
But as of today, further progress has been made and we are more certain it can be done.
But it will be quite challenging though the difficult parts have now been overcome.
There're still many small thorny areas.
For example, the division operation / behaves differently in Python 3 compared to Python 2.7.
4/2 = 2 (Python2.7)
4/2 = 2.0 (Python 3)
This means that if an old challenge's solution is 786 and you submit 786, it would be checked as Wrong because Python 3 gives 786.0 (whereas you would have passed the challenge before).
So there's tons of things to change and check.
We'll attempt the porting slowly so as not to break anything - if we proceed with the porting.
The challenges need to be checked to ensure they don't break. Anyone can help with this part? Just solving it when it's running the new code?
Last edited on 2020-05-20 02:43:57 by Pha. Sphinx