Python 3.11.3 (main, Jun  5 2023, 09:32:32) [GCC 13.1.1 20230429] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> print "Hello World"
  File "<stdin>", line 1
    print "Hello World"
    ^^^^^^^^^^^^^^^^^^^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?

I hope this doesnt reflect on the Quality of this community 🤡

top 8 comments

sorted by: hot top controversial new old

[–] [email protected] 30 points 1 year ago (1 children)

It's Python 2. Not sure why anyone's writing Python 2 in 2023, but it's valid code.

[–] [email protected] 8 points 1 year ago (1 children)

Some people have legacy codebases and haven't been able to justify the workload to migrate it 😭😭😭

[–] SoftwareLeopardx3 3 points 1 year ago

So common in consulting. Many customers only want new things and feel like they shouldn't have to keep paying once an initial product has been delivered. But needs change, tech moves on and things need refreshing or replacing. The hardest situation is when the client has no in-house expertise so can only assume you're trying to fleece them for more money.

[–] Ategon 13 points 1 year ago (1 children)

The print call there is from python 2. I can do some editing to add in the brackets in a bit

[–] [email protected] 8 points 1 year ago (1 children)

I was a little cheeky there. But in all seriousness python 2 is End-of-Life and no one should use it anymore.

[–] [email protected] 9 points 1 year ago (2 children)

Come on, Python 2 only has 16 critical vulnerabilities. Live dangerously 🙃.

[–] [email protected] 2 points 1 year ago

Shoutouts to all people out there maintaining legacy code 🫣

[–] qwop 1 points 1 year ago

Although "critical" by CVE standards could just mean ReDoS for some non user facing code and which clearly is not a security issue but still of course requires urgent dependabot warnings on some parent package which doesn't even use the not at all vulnerable code anyway...