You only have to add brackets to the print statements to make that particular piece of code work in both Python 2 and Python 3.
I think it's time to take a step back and ask why getting _six_ lines of code entered correctly has been such an uphill task for you, taking several days, and you're _still_ not there yet. There's nothing wrong with the "try:" statement, and if it's entered correctly, it will be fine.
I applaud attempts to learn programming but if you're having this much trouble to even take the first step, then you have to start considering what's wrong with your approach and the programming environment that you're using. For example, not even being able to cut-and-paste is like having a hand tied behind your back.
Point1. Are you testing your initial attempts at writing Python on a Raspberry Pi or on your main computer? _Is_ a Raspberry Pi your main computer? You'd be better off taking the first steps on the same machine that you're reading these newsgroups with. And do figure out how to cut-and-paste at least.
Point2. Given that most Python examples on the web are Python2 and most users seem to be putting off updating to Python3 until the associated tools have caught up, you'd be very much better off starting with Python2. If you're hoping to get support from web-users, then that's the version of Python that gets the support. There's not that many differences with Python3, so it shouldn't be difficult to update later when the time is right.
Point3. Which OS are you using on the Pi? RISCOS? Again, that's not the one to go for if you want support. Not many people here use it. In fact, I'd only recommend it to people that used it during the 1980s and already know exactly what they're doing with it. _Raspbian_ is the one to use if you want support. Raspbian might be a little bit more fiddly to set up, to boot into the desktop automatically, and to figure out how to install software from the Raspbian repositories (using the Synaptic app). But Raspbian is a modern Linux distro with plenty of web support with web tutorials and videos.
Point4. If you get the above sorted out, you should find it easier to ask questions because you can run Python code from the command line and cut-and-paste the exact error report into a forum post.
For example, if I have a file containing the work "try:", but say I forgot to add the colon on the end, then if I ran it from the command line, I'd get an error. I'll do that now and cut-and-paste the result.
[dsf: /work/tmp]$ echo "try" >test.py # that creates the one liner [dsf: /work/tmp]$ chmod a+x test.py # that adds the execute flag [dsf: /work/tmp]$ python test.py # now i run it File "test.py", line 1 try ^ SyntaxError: invalid syntax [dsf: /work/tmp]$See? Easy. That's what you should be trying to do now: making it easier for yourself.