I recently stumbled on the following return statement written in Python 2:

Tossing this into my PyDev 3.5.2 compiler I got a lexical error and when I removed the ' ' surrounding the return statement it went away. I never used Python 2 so I am left wondering if the statement is still equivalent and what exactly the purpose of putting ' ' around a return statement was in Python 2.

The quotes or backtics were obviously a mistake and weren't meant to be there.

The return statement is a red herring.

Backticks were deprecated and replaced by the repr() function. So, you actually changed the meaning of that function by removing the backticks and not replacing them with anything.

https://stackoverflow.com/questions/...nterpreter-num

etc.

1 members found this post helpful.

Ah I see okay good to know!

Maybe I could pick your brain a bit more hydrurga. I believe I ran into another red herring. Did the call: log and sys have a special meaning that changed from python 2 to python 3? For instance, the code throwing an error is:

and the compiler is saying: Undefined variable: log and Undefined variable: sys

Okay so sys.exc_traceback was definitely removed. Still not sure about log(). Also, not sure what I should be changing sys.exc_traceback too. I found documentation about how its been changed but not what its been replaced by lol

I have an earth-shattering confession to make, vysero. I hadn't even heard of backticks in Python 2 before you posted your thread, but I decided to help you by searching on the web for "Python 2" "Python 3" backticks and came up with the info. So, my brain isn't really worth picking.

A search on the internet shows that sys.exc_traceback is now deprecated and replaced by exc_info() - https://docs.python.org/2/library/sys.html

It looks as if the log() function comes with the logging module (https://docs.python.org/2.6/library/...ml#logging.log). You'll probably need to look at how the logging module works in Python 3 to figure out why the function isn't recognised. The module has perhaps changed in the way it is loaded or its functions called - https://docs.python.org/3/howto/logging.html

Converting between a Python 2 script and a Python 3 one, without looking into how the script actually works, is a wee bit risky because some changes enforced between the two versions may have subtle effects within the script.

Still very helpful, thank you. However, for some reason my compiler is having a problem with sys and not with the .exe_traceback (which I changed to .exe_info() btw).

What problem is it having with sys?

Okay I think I figured out the problem. I believe, that sys did in fact need to be imported in py2; however, since sys was being imported by all the other scripts that were calling this particular script the fact that it was never imported here made no noticeable difference. So basically, this particular script had an error that was never noticed for over 12 years lol, oh well!