←back to thread

620 points tambourine_man | 3 comments | | HN request time: 0.414s | source
1. mos_basik ◴[] No.43754980[source]
Landing in 3.14? Nice, but also oof, that's probably not getting to my employer's codebase for a year or two. And it sounds like it could really solve some problems for us, too.

Paging asottile - any plans to make a `future-tstrings`? :)

`future-fstrings` (https://pypi.org/project/future-fstrings/) was a real QOL improvement for our team for a year or 2 around 2019 before we got onto Python 3.x.

replies(2): >>43755099 #>>43755409 #
2. pauleveritt ◴[] No.43755099[source]
Some prior art: https://pypi.org/project/tagged/

In fact, the repo of a companion project from the author has the ticket that spawned the work leading to t-strings: https://github.com/jviide/htm.py/issues/11

3. ayhanfuat ◴[] No.43755409[source]
I asked asottile for his opinion on PEP 750 (or rather, a previous version of it), and he wasn’t really in favor. So I think it’s unlikely that we’ll see a future-tstrings from him. :)