On 07/18/2016 02:45 PM, Brett Cannon wrote: > On Mon, 18 Jul 2016 at 14:35 Alexander Belopolsky wrote: >> On Mon, Jul 18, 2016 at 5:01 PM, Jonathan Goble 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*() ? bytes.fromsize() sounds good to me, thanks for brainstorming that one for me. I wasn't really happy with 'size()' either. -- ~Ethan~
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4