←back to thread

Python’s new t-strings

(davepeck.org)
620 points tambourine_man | 2 comments | 21 Apr 25 04:31 UTC | HN request time: 0.452s | source
Show context
damnitbuilds ◴[21 Apr 25 08:00 UTC] No.43749409[source]▶
I enjoy f-strings, I guess some people need these.

And I love Python but, having been through 2->3 ( occasionally still going through it! ) whenever I see a new language feature my first thought is "Thank goodness it doesn't break everything that went before it".

replies(1): >>43749513 #
stavros ◴[21 Apr 25 08:20 UTC] No.43749513[source]▶
Yeah but it's been 17 years, maybe it's time to put the PTSD behind us. We're almost at a point where the current generation of programmers wasn't even programming when that happened.
replies(3): >>43749798 #>>43749836 #>>43751267 #
1. rglullis ◴[21 Apr 25 09:05 UTC] No.43749798[source]▶
> We're almost at a point where the current generation of programmers wasn't even programming when that happened

I've been programming with Python since 2006, I think most of the systems were based on 2.4 at the time. I've been one of those who switched to Python 3 somewhat late, waiting for some major libraries to ship python 3 packages - celery and Twisted were one of the biggest holdouts - so I remember that the first project where all my dependencies were ready for python 3 was around 2015.

This is to say: even seasoned developers who were conservative around the migration have spent more time working with Python 3 than Python 2. There simply is no reason anymore to be talking about python 2.

replies(1): >>43750594 #
2. kstrauser ◴[21 Apr 25 11:14 UTC] No.43750594[source]▶
The last time I touched a large Py2 project was in 2018 when I ported it to Py3. So, I have 18 years of Py2, probably 6 years of overlap, and 7 years of pure Py3. That means I still have a lot more Py2 than Py3 time.

Buuuttt, I'm so over the transition. It’s ancient now and I agree that we can stop fretting about it.