Because they broke backward compatibility in very annoying ways without providin... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

musicale on Nov 15, 2019 | parent | context | favorite | on: Why Is the Migration to Python 3 Taking So Long?

Because they broke backward compatibility in very annoying ways without providing a fallback mechanism.

I still haven't forgiven them for killing the print statement, which could have peacefully coexisted with a print() function.

mixmastamyk on Nov 15, 2019 | [–]

Bugged me for a while five years ago. Then I moved everything to logging and use an editor snippet: pr<TAB> —> print(‘foo:’, %cursor%)

akx on Nov 15, 2019 | [–]

Having two ways to do the same thing is against The Zen of Python.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact