Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure to start with Python 3.6.3 #7

Open
eekee opened this issue Jan 22, 2018 · 5 comments
Open

Failure to start with Python 3.6.3 #7

eekee opened this issue Jan 22, 2018 · 5 comments
Labels

Comments

@eekee
Copy link

eekee commented Jan 22, 2018

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
Copy link
Author

eekee commented Jan 22, 2018

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
Copy link

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
Copy link

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
Copy link
Author

eekee commented Feb 2, 2018

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
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants