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 mark.dickinson
Recipients eric.smith, facundobatista, mamrhein, mark.dickinson, rhettinger, skrah
Date 2019-12-17.21:54:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1576619696.92.0.252151337767.issue39077@roundup.psfhosted.org>
In-reply-to
Content
[Eric]

> Is that the "0" here: [...]

Yes, sorry; that could have been clearer.

> In particular, what if you specify a different alignment type with the pre-width 0?

Right, that's the critical question here. For floats and ints, an explicitly-specified alignment type overrides the implicit "=". But Decimal raises. The Decimal behaviour seems more reasonable, but the float and int behaviours are more historically baked-in, and riskier to change.

And then there's a parallel question with the fill character: should an explicitly-given fill override the "0"-fill character that's implicit in that "[0]"? int and float say "yes". Decimal says "ValueError".
History
Date User Action Args
2019-12-17 21:54:56mark.dickinsonsetrecipients: + mark.dickinson, rhettinger, facundobatista, mamrhein, eric.smith, skrah
2019-12-17 21:54:56mark.dickinsonsetmessageid: <1576619696.92.0.252151337767.issue39077@roundup.psfhosted.org>
2019-12-17 21:54:56mark.dickinsonlinkissue39077 messages
2019-12-17 21:54:56mark.dickinsoncreate