A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2014-August/135661.html below:

[Python-Dev] Surely "nullable" is a reasonable name?

[Python-Dev] Surely "nullable" is a reasonable name? [Python-Dev] Surely "nullable" is a reasonable name?Antoine Pitrou antoine at python.org
Mon Aug 4 19:53:19 CEST 2014
Le 04/08/2014 13:36, Alexander Belopolsky a écrit :
>
> On Mon, Aug 4, 2014 at 12:57 PM, Ethan Furman <ethan at stoneleaf.us
> <mailto: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.

But here the receiving type can be an int.

Regards

Antoine.


More information about the Python-Dev mailing list

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