[Python-Dev] PEP 467: next round
Brett Cannon
brett at python.org
Mon Jul 18 17:45:27 EDT 2016
More information about the Python-Dev mailing list
Mon Jul 18 17:45:27 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 14:35 Alexander Belopolsky < alexander.belopolsky at gmail.com> 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()? > Or bytes.fromsize() to stay with the trend of naming constructor methods as from*() ? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20160718/f53951cd/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