[Python-Dev] PEP 467: next round
Brett Cannon
brett at python.org
Mon Jul 18 18:52:46 EDT 2016
More information about the Python-Dev mailing list
Mon Jul 18 18:52:46 EDT 2016
- Previous message (by thread): [Python-Dev] PEP 467: next round
- Next message (by thread): [Python-Dev] PEP 467: next round
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 18 Jul 2016 at 15:49 Random832 <random832 at fastmail.com> wrote: > On Mon, Jul 18, 2016, at 17:34, Alexander Belopolsky wrote: > > On Mon, Jul 18, 2016 at 5:01 PM, Jonathan Goble <jcgoble3 at gmail.com> > > wrote: > > > > > full(), despite its use in numpy, is also unintuitive to me (my first > > > thought is that it would indicate whether an object has room for more > > > entries). > > > > > > Perhaps bytes.fillsize? > > > > I wouldn't want to see bytes.full() either. Maybe bytes.of_size()? > > What's wrong with b'\0'*42? > It's mentioned in the PEP as to why. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20160718/88b021fe/attachment.html>
- Previous message (by thread): [Python-Dev] PEP 467: next round
- Next message (by thread): [Python-Dev] PEP 467: next round
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list