Post-black
string format conversion
#47
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Close #46, at least for the vast majority of cases, particularly those involving much longer lines, with mixed and/or non f-string formatted strings
Note there are lots of new-line characters peppered about the strings especially for user messages, which I will remove (they are not useful since users will be viewing these on terminals or IDEs or similar of variable width where standard line wrapping will apply for readability, and these custom new lines could cause weird gaps and wrapping issues) but I will do that as a separate issue since it is distinct and a significant task in its own right. I have generally only removed/added new line characters to preserve the behaviour of the string with any change of formatting.
I will do a self-review before merging since there is so little testing at present (one of the next priorities it to get some and increase coverage!) so I won't be convinced I haven't inadvertently broken something during the conversion until I've checked the pushed line changes carefully.