History/preference aside, I think you’re being a bit hyperbolic regarding the co... | Hacker News

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

		rsfern on Oct 6, 2020 \| parent \| context \| favorite \| on: Python 3.9 History/preference aside, I think you’re being a bit hyperbolic regarding the cost of removing the print statement. It’s like the most trivial broken feature to fix with 2to3. I’ve definitely run into issues 2to3 couldn’t automatically fix (encoding issues in some py2-only lib I needed to use IIRC), but upgrading print doesn’t really have much overhead.

mafuy on Oct 6, 2020 [–]

You assume people know that 2to3 exists, and that they will all the time use it to fix copied code snippets. I think neither is true.

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