➜

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 terry.reedy
Recipients docs@python, eric.smith, louielu, serhiy.storchaka, terry.reedy, vstinner, xiang.zhang, ztane
Date 2017-04-05.11:00:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1491390054.02.0.257695704014.issue28415@psf.upfronthosting.co.za>
In-reply-to
Content 
(Response to what I believe is latest patch.)  In msg278666, my two suggestions were 'either...or', not both.  The list came from Antti's msg278528, but the correct list for Python appears to be different, and different for bytes and unicode.  When I made the suggestion, I did not realize that 'exactly' was repeated for each conversion type in a table.  As a note, I think the following might work. "For <list of> conversion types, the 0-conversion flag has effect even when a precision is given."

I also think that 'exactly could be dropped when it is not exactly true.
History
Date User Action Args
2017-04-05 11:00:54terry.reedysetrecipients: + terry.reedy, vstinner, eric.smith, docs@python, serhiy.storchaka, ztane, xiang.zhang, louielu
2017-04-05 11:00:54terry.reedysetmessageid: <1491390054.02.0.257695704014.issue28415@psf.upfronthosting.co.za>
2017-04-05 11:00:54terry.reedylinkissue28415 messages
2017-04-05 11:00:53terry.reedycreate