2 ms·
Well, yes, porting large projects to Py3 is not trivial. That's why they had, what, around 5 years to do it since the 2.7 EOL was extended to 2020? I think mo
by raverbashing 7y ago
Well, yes, porting large projects to Py3 is not trivial.
That's why they had, what, around 5 years to do it since the 2.7 EOL was extended to 2020?
I think most of the problems you encountered would be solved by the six library, btw.
But the most annoying bugs were those were some Python 2 quirk was "just working" (like comparing strings to integers in Python 2) or the conversion of ints and floats and then it correctly broke on Python 3.
- strenholme 7y agoUsing the six library is one way to make a large project being written from the ground up run in both Python2 and Python3. For this particular project, I would had needed to get the code to run in both Python3 and an ancient version of Python2 made back when boost.python was still a thing, so six would be out of the question.