RetroSearch Browse

Fri Apr 26 01:09:41 CEST 2013 · https://mail.python.org/pipermail/python-dev/2013-April/125561.html

We just fixed NoneType() to return None instead of raising an exception.

Another use-case for calling NoneType is working with ORMs:

result = []
for field in row:
      type = get_type(field)      # returns int, bool, str, NoneType, ...
      result.append(type(field))

if field is None, the resulting call is NoneType(None), and since NoneType doesn't take any parameters we get an exception.

Is it worth filing a bug to have NoneType accept one optional argument, which defaults to None, and must be None, else 
raise an exception?

Or should it be:

class NoneType:
     def __new__(cls, *args, **kws):
         return None

Which is basically what my 2.x none() helper function does...

--
~Ethan~

Showing content from https://mail.python.org/pipermail/python-dev/2013-April/125561.html below: