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 vinay.sajip
Recipients Ramchandra Apte, eric.araujo, eric.smith, meador.inge, ncoghlan, terry.reedy, vinay.sajip
Date 2012-06-03.18:28:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
It seems like the patch doesn't consider mixing of positional and keyword arguments: if you have the format string "{foo} {} {bar}", then manual will be set to True when "foo" is seen as the field_name, and fail soon after when "" is seen as the field_name the next time around.

So, the test should include something which shows that

fmt.format("{foo} {} {bar}", 2, foo='fooval', bar='barval') returns "fooval 2 barval", whereas with a format string like "{foo} {0} {} {bar}" or "{foo} {} {0} {bar}" you get a ValueError.

Also, why "automatic field numbering" vs. "manual field specification"? Why not "numbering" for both?
Date User Action Args
2012-06-03 18:28:13vinay.sajipsetrecipients: + vinay.sajip, terry.reedy, ncoghlan, eric.smith, eric.araujo, meador.inge, Ramchandra Apte
2012-06-03 18:28:13vinay.sajipsetmessageid: <>
2012-06-03 18:28:12vinay.sajiplinkissue13598 messages
2012-06-03 18:28:12vinay.sajipcreate