Eric Osborne <e...@notcom.com> added the comment: Cool, I will kick it over to python-ideas. I checked in some code to handle the format string and it's a lot like what you're suggesting, so I'll leave that in there and see what happens. Thanks!
eric On Tue, Feb 13, 2018 at 11:56 PM Nick Coghlan <rep...@bugs.python.org> wrote: > > Nick Coghlan <ncogh...@gmail.com> added the comment: > > Aye, definitely worth a thread on python-ideas. My rationale for > suggesting something based on the built-in numeric codes is that it makes > it straightforward for *users* to transfer knowledge from that > mini-language. > > As far as parsing goes, I was thinking of something along the lines of the > following naive approach: > > typechar = fmt[-1:] > if not typechar or typechar not in ("b", "n", "x"): > return super().__format__(fmt) > prefix, group_sep, suffix = fmt[:-1].rpartition("_") > if prefix and prefix != "#" or suffix: > return super().__format__(fmt) > field_width = self._calculate_field_width(typechar) > return format(int(self), > f"{prefix}0{field_width}{group_sep}{type_char}") > > ---------- > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <https://bugs.python.org/issue32820> > _______________________________________ > ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32820> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com