+1 to start using and suggesting f-string in new PRs I agree to avoid bulk updated only to use f-string in old code.
I think we can write a priority list of string formatting styles to help new and old contributors in following the same code style in all PRs. I will suggest this order: 1) f-string 2) %-formatting 3) format On Tue, Jul 21, 2020 at 10:21 AM Adam Johnson <m...@adamj.eu> wrote: > +1 to allowing f-strings. > Mariusz' position dropping .format() seems reasonable to me too.... > On Tue, 21 Jul 2020 at 09:00, laym...@gmail.com <laymon...@gmail.com> wrote: >> I personally like to use f-strings wherever it makes sense, so +1. >> I agree with Mariusz. I think we should only allow %-formatting and >> f-strings from now on. >> And yes, bulk updates should not be done. ... >> On Tuesday, 21 July 2020 at 14:28:54 UTC+7 Mariusz Felisiak wrote: >>> I will not stand against f-strings, I think we can allow them. My main >>> concerns is readability. ... >>> I'm strongly against any bulk updates to conform to this style.... >>> I would also be in favor of keeping only %-formatting and f-strings in >>> Coding style docs.... -- Paolo Melchiorre https://www.paulox.net -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAKFO%2Bx6JmXnDaamf8TTE5S3XGXGWbV0MfPkKboS6ZgViN0xJRA%40mail.gmail.com.
