This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author aeros
Recipients JulienPalard, Mariatta, aeros, docs@python, eric.smith, fdrake
Date 2019-10-03.01:35:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1570066544.09.0.167907923987.issue38351@roundup.psfhosted.org>
In-reply-to
Content
> I definitely think we should not modify any code in the stdlib just to switch to f-strings.

Does this also apply to updating code to use f-strings in an area that's already being modified for a functional purpose? 

I agree that that we shouldn't update stdlib code for the sole purpose of switching to f-strings, but if a function or method is already being changed for another purpose, I don't think updating the formatting to use f-strings is an issue. This would probably have to be decided on a case-by-case basis though.
History
Date User Action Args
2019-10-03 01:35:44aerossetrecipients: + aeros, fdrake, eric.smith, docs@python, JulienPalard, Mariatta
2019-10-03 01:35:44aerossetmessageid: <1570066544.09.0.167907923987.issue38351@roundup.psfhosted.org>
2019-10-03 01:35:44aeroslinkissue38351 messages
2019-10-03 01:35:44aeroscreate