Hacker News Reader

Comment by baq | Hacker News Reader

1. forget python 2.7 exists

2. can't help with the whitespace, sorry; also take care handling Makefiles

I have worked at places where they insisted on 2 space indention, which made it much much harder to read the code and follow indention levels. It was just stupid of course. That's what really turned me off of python. I know there are bad formatting options for c style languages, and the editor should make it clear. but 2 spaces is too little, too late.

> 1. forget python 2.7 exists

But it doesn't work this way. You don't work strictly with the language itself, you work with the whole ecosystem. Libraries, tools, snippets, SO questions, etc. And many of those are still in 2.7 or at least need to specify different solutions for 2.7... It is still a pain.

> Libraries, tools, snippets, SO questions, etc. And many of those are still in 2.7 or at least need to specify different solutions for 2.7... It is still a pain.

Admittedly there were some libraries that took a long time to switch, but at this point there is no serious library left, that did not make the switch.

Exactly. I've gone farther even, and this is my motto now:

    Python 3.6+ or burn it to the ground

I mself still have to port a few projects yet, but those that got stuck in 2.7-3.5 land are en route to dying a fiery death, and being reborn in 3.6+ (3.8 where applicable, 3.6 as the lowest I'm willing to accept).

Maya is still embedding Python 2.x. Soon (tm)...

Makefiles are half the reason I enable visible whitespace in my editors.

Reply on news.ycombinator.com