Platform Development • Re: I created a Python 3 port of UXP out of boredom...

There is one BIG issue I just thought of as I was finishing this work, though... if a developer needs to go back in time through git history to before we did the Python 3 switch... they would still need Python 2.x in order to build the system at that point. I've been thinking about whether this needs to be addressed... and I came up with two basic ideas...

As already touched on on the repo, I don't think this is a big issue. We've had multiple breaking changes in history. e.g. if you go back far enough, then Pale Moon will stop building on MSVC because VS2022 isn't backwards compatible to the specifics of very old code bases that were developed against, say, 2008 or older compilers. On Windows it won't even be much of an issue since we do have python 2 and 3 in our mozilla build tools, just needing to be references properly. It doesn't matter when you make this changeover to python3, delaying it because of perceived build issues won't be a problem any more now than it will in the future; the breaking changes won't go away by waiting until it becomes impossible to build on more systems...