Much Ado About None: Sentinel Values in Python

Join the discussion

• Hacker News
• I hate sentinel values. Even/especially with AI-generated code.

  1. If your date does not have a value, do not return 0, an empty string, or None. Use a discriminated union and model your domain rigorously.

  2. If your data model accepts None/undefined as a value, that should translate to your business model as well. For example

  3. Do not make your `name` field as `string | undefined` just because there might be an intermediate loading or processing state. It's better to model that as something like `Loaded<string>` where Loaded is something like a Result or Optional type (though ideally more rigorously defined)

  Here is what I've done for years in TypeScript, though now in a nice package thanks for AI: https://github.com/shepherdjerred/monorepo/blob/main/package...

  by shepherdjerred
• I have a library that's approximately half joking that I use for (sentinel and other) special value constants. If you like reading test suites, this one will get ya:

  https://github.com/nucypher/constantSorrow/blob/master/tests...

  by jMyles
• I just return a customized Exception type. Works about the same.
  by est
• Here is the sample code from the article:

      > MISSING = sentinel("MISSING")
  
      > def update_email(user_id: int, email: str | None | MISSING = MISSING) -> None:
      >     if email is MISSING:
      >         return  # nothing to update
      >     elif email is None:
      >         db.delete_email(user_id)
      >     else:
      >         db.set_email(user_id, email.lower())  # narrowed to str
  

  I see this style frequently from long time Python programmers. The language is so dynamic that people begin to think this is a good way to program. Hot take: It is not. Why not two different functions called delete_email() and set_email()? That would be more clear.
  by throwaway2037
• I like it. I can't see how to do better while remaining compatible with Python idioms.
  by chowells
• "A simple cache returns None both for a missing key and for a key that maps to None."

  No, it returns KeyError. Or at least it should.

  by RantyDave
• When I was writing a bunch of Lua, I was a big fan of having a None sentinel value (Lua uses 'nil' for representing absence) and it was useful for a lot of things similar to Pydantic's MISSING.

  This distinction is something that I think is actually handy about JavaScript, and distinguishing between 'null' and 'undefined' is sometimes useful for similar reasons.

  by lpghatguy
• So much trouble to avoid introducing the optional monad.
  by pwdisswordfishq