Eli Bendersky added the comment: On Wed, Aug 14, 2013 at 12:07 PM, Ethan Furman <rep...@bugs.python.org>wrote:
> > Ethan Furman added the comment: > > > Eric V. Smith added the comment: > > > > I assumed we'd want it to look like the str() version of itself, always. > But it's debatable. > > An IntEnum's str and repr should be (and any format or % codes that are > the equivalent) the Enum str and repr. The % > and format codes that specifically call for a numeric representation > should give that numeric representation (format is > good here, % is not). > > > For format, I think the question is "should an IntEnum format like an > int, with the wacky exception of a specifier of '', or should it always > format like a str?" > > > > I think for format we should treat IntEnums as ints unless the s or r > codes are specifically used. > As I wrote above, I rather see it differently. The original intent of Enums was to have string representation in most cases. So this should be the default, since most of the time this is what the user wants. No one really passes explicit s/r codes. In the minority, specialized cases, where the user wants to force int-like formatting, then the number should be given and not the member name. This would also be consistent with non-decimal formatting options like %x and the .format equivalent. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue18738> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
