search

SBTCVM / SBTCVM-Mark-2

[no longer supported, please see SBTCVM-Gen2-9] Simple Balanced Ternary Computer Virtual Machine: Mark 2 is a simple Balanced Ternary VM programmed in python and Pygame.
https://sbtcvm.blogspot.com/
GNU General Public License v3.0
14 stars 5 forks source link

Failure to start with Python 3.6.3 #7

Open eekee opened 6 years ago

eekee commented 6 years ago

Neither launcher.py nor SBTCVM_MK2.py will start with Python 3.6.3. I assume others also won't, as it's a syntax error in using print:

(SBTCVM-Mark-2-master) 55 % python SBTCVM_MK2.py
  File "SBTCVM_MK2.py", line 18
    print "SBTCVM Mark 2 Starting up..."
                                       ^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print("SBTCVM Mark 2 Starting up...")?
(SBTCVM-Mark-2-master) 56 % python launcher.py
  File "launcher.py", line 22
    print "SBTCVM Desktop v3.0"
                              ^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print("SBTCVM Desktop v3.0")?
(SBTCVM-Mark-2-master) 57 % python launcher.py
  File "launcher.py", line 22
    print "SBTCVM Desktop v3.0"
                              ^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print("SBTCVM Desktop v3.0")?

Sorry to do this, I loathe dealing with upgrade issues myself, but with Python 3.0 having been released 10 years ago, I thought I ought to at least file it. I'll install Python 2.7 for now, not expecting you to fix it overnight. :)

eekee commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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.