Opened 3 years ago
Closed 3 years ago
#33034 closed Cleanup/optimization (wontfix)
Change % to f-strings in django documentation
| Reported by: | Athul Muralidhar | Owned by: | Athul Muralidhar |
|---|---|---|---|
| Component: | Documentation | Version: | 3.2 |
| Severity: | Normal | Keywords: | documentation |
| Cc: | Athul Muralidhar | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
As a frequent reader (and lover) of the django documentation, I was just wondering why we are still sticking around with % in the strings returned by some class methods.
One example is here:
https://docs.djangoproject.com/en/3.1/topics/db/examples/many_to_one/ NB the __str__ method does not use f-strings
Note:
- This maybe a minor issue and any technical or other considerations that prevent the above change should automatically lead to the closure of this ticket :)
Change History (2)
comment:1 by , 3 years ago
| Cc: | added |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
comment:2 by , 3 years ago
| Easy pickings: | unset |
|---|---|
| Resolution: | → wontfix |
| Status: | assigned → closed |
| UI/UX: | unset |
Note:
See TracTickets
for help on using tickets.
Thanks for the ticket, however in discussion on the mailing list related to the ticket #29988 we agreed that there is no need to make any bulk updates related with f-strings. Also, I don't see a problem with %-formatting.