Sorry. I meant to be terse, but wasn't clear enough. I meant the method name. If it takes a `delimiter` karg, it would be consistent to call the operation `delimit`. On Tue, 2 May 2017 13:06 Carl Smith, <carl.input@gmail.com> wrote:
Couldn't it just be named `str.delimit`? I totally agree with Steve for what it's worth. Thanks for everything guys. Best,
On Tue, 2 May 2017 13:02 Joao S. O. Bueno, <jsbueno@python.org.br> wrote:
On 1 May 2017 at 11:04, Juancarlo Añez <apalala@gmail.com> wrote:
On Mon, May 1, 2017 at 9:38 AM, Nick Coghlan <ncoghlan@gmail.com>
just support two keyword arguments to hex(): "delimiter" (as you suggest) and "chunk_size" (defaulting to 1, so you get per-byte chunking by default)
I'd expect "chunk_size" to mean the number of hex digits (not bytes)
wrote: per
chunk. So do I. Moreover, if "1" is for two digits, there is no way to specify single digits - for little use we can perceive for that.
Maybe it does not need to be named "chunk_size" - "digits_per_block" is too big, but is precise.
Also, whatever we think is good for "hex" could also be done to "bin" .
Cheers,
-- Juancarlo Añez
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/