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 r.david.murray
Recipients eric.smith, r.david.murray, rhettinger, serhiy.storchaka, veky
Date 2015-03-16.15:41:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1426520475.09.0.61442040565.issue23624@psf.upfronthosting.co.za>
In-reply-to
Content
Backward compatibility does not mean "matches the docs", it means "if we change this, someone's existing code is likely to break".  That does not prevent us from making at-the-margin changes in a feature release, but it is still a bar to be overcome in making such a change, and the consensus here is that it doesn't meet that bar.

Your primary argument seems to be the desire to make it easy to switch to center if the width of the field becomes a variable.  But you note yourself that you do not need to do this; format is quite capable of handing a variable width field.

So, there also does not seem to be sufficient motivation to add this feature.  If you wish to pursue this further, posting your proposal for a keyword for center and the motivation to python-ideas would be the way to proceed.  If you gather a consensus of support there, you can propose a new enhancement request issue with a link to the python-ideas discussion.  (Or, in the unlikely case that the consensus is that center's algorithm should change, we can reopen this issue.)
History
Date User Action Args
2015-03-16 15:41:15r.david.murraysetrecipients: + r.david.murray, rhettinger, eric.smith, serhiy.storchaka, veky
2015-03-16 15:41:15r.david.murraysetmessageid: <1426520475.09.0.61442040565.issue23624@psf.upfronthosting.co.za>
2015-03-16 15:41:15r.david.murraylinkissue23624 messages
2015-03-16 15:41:14r.david.murraycreate