On 4 Aug 2014 18:16, "Oleg Broytman" <p...@phdru.name> wrote: > > Hi! > > On Mon, Aug 04, 2014 at 05:12:47PM +1000, Larry Hastings < la...@hastings.org> wrote: > > "nullable=True", which means "also accept None > > for this parameter". This was originally intended for use with > > strings (compare the "s" and "z" format units for PyArg_ParseTuple), > > however it looks like we'll have a use for "nullable ints" in the > > ongoing Argument Clinic conversion work. > > > > Several people have said they found the name "nullable" surprising, > > suggesting I use another name like "allow_none" or "noneable". I, > > in turn, find their surprise surprising; "nullable" is a term long > > associated with exactly this concept. It's used in C# and SQL, and > > the term even has its own Wikipedia page: > > > > http://en.wikipedia.org/wiki/Nullable_type > > In my very humble opinion, "nullable" is ok, but "allow_none" is > better.
Yup, this is where I stand as well. The main concern I have with nullable is that we *are* writing C code when dealing with Argument Clinic, and "nullable" may make me think of a C NULL rather than Python's None. Cheers, Nick. > > Oleg. > -- > Oleg Broytman http://phdru.name/ p...@phdru.name > Programmers don't die, they just GOSUB without RETURN. > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
