Failure to start with Python 3.6.3

[eekee]

Failure to start with Python 3.6.3

[eekee]

PyGame's "getting started" page nearly gave me a heart attack, it implied PyGame for Python 2.7 doesn't exist any more. I went to the download page and was glad to find it's only 2 'patchlevel' version numbers behind. :)

[ThomasTheSpaceFox]

tried to fix the problem, but turns out i broke a bunch of things and had to revert said fix. it is a problem, python 3 and python 2 are quite different beasts, and working with both feels a lot like baking 2 different kinds of cake in the same pan at once.

[ThomasTheSpaceFox]

This does highlight an unresolved issue with the redesigned version of the codebase. eekee, when you have the time could you check out the newest discussion over at @SBTCVM/core-devs ?

[eekee]

Further to discussion in @SBTCVM/core-devs , are we leaving it as Python 2 unless Mark 3 is not ready when the end of Python 2's life gets near? I support this.

[ThomasTheSpaceFox]

yea Thats basically the idea. though it probably be best if we start the actual porting in say mid 2019? given, we do have plenty of code laying around, and it might take a month or so, though i don't want to wait to the last minute either.