Alexander Belopolsky alexander.belopolsky at gmail.com
Mon Aug 4 19:36:39 CEST 2014

• Previous message: [Python-Dev] Surely "nullable" is a reasonable name?
• Next message: [Python-Dev] Surely "nullable" is a reasonable name?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Mon, Aug 4, 2014 at 12:57 PM, Ethan Furman <ethan at stoneleaf.us> wrote:

> 'allow_none' is definitely clearer.


I disagree. Unlike "nullable", "allow_none" does not tell me what happens
on the C side when I pass in None.  If the receiving type is PyObject*,
either NULL or Py_None is a valid choice.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20140804/38ed3c22/attachment.html>

---

• Previous message: [Python-Dev] Surely "nullable" is a reasonable name?
• Next message: [Python-Dev] Surely "nullable" is a reasonable name?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list