-
Notifications
You must be signed in to change notification settings - Fork 26
[Maintenance/Refactoring] Unify String Formatting In All Files #228
Comments
This is In any event, the person implementing this should definitely read about how to control the formatting. |
I'm not so sure we should abandon indexing blindly as a "this is py2.6" reason; there are certain instances in which the indexing is specifically needed to get the string sequence correct: gem-plotting-tools/utils/anautilities.py Lines 155 to 157 in 135f4d8
(just the first example I found, here indexing is mandatory). I would rather say that indexing can be dropped when it is not needed. |
indeed, this was the point of my last comment. |
Some (all?) of this formatting has been done in #252. The remaining statements do not deserve a fix in legacy. |
Brief summary of issue
Spurred by discussion with @jsturdy we should unify string formatting to use
str.format
rather than%
operator.Types of issue
Expected Behavior
All string formating and file I/O operations with formatted strings should default to using
str.format
rather than%
operator.Current Behavior
Older code blocks still have statements like:
Instead of using
str.format
, e.g.Context (for feature requests)
Consistency.
The text was updated successfully, but these errors were encountered: