This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients Yury.Selivanov, brett.cannon, georg.brandl, larry, serhiy.storchaka, taleinat, vajrasky, zach.ware
Date 2014-01-22.10:31:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390386689.04.0.659366003511.issue20341@psf.upfronthosting.co.za>
In-reply-to
Content
> I don't remember who specifically needed the nullable ints, so I just added a bunch of Derby contestants.

There are no much need in nullable ints, if they are needed, different use cases require different semantic. I don't think we can now write general converters which will cover different use cases. May be in 3.5, when behavior changes will be possible.

I know only one use case for nullable Py_ssize_t converter (and mmap_convert_ssize_t is much simpler). itertolls.repeat doesn't need it, because it shouldn't accept None.

Let defer this issue until most of code will be converted. Then we can accumulate statistic about nullable in converters.
History
Date User Action Args
2014-01-22 10:31:29serhiy.storchakasetrecipients: + serhiy.storchaka, brett.cannon, georg.brandl, taleinat, larry, Yury.Selivanov, zach.ware, vajrasky
2014-01-22 10:31:29serhiy.storchakasetmessageid: <1390386689.04.0.659366003511.issue20341@psf.upfronthosting.co.za>
2014-01-22 10:31:29serhiy.storchakalinkissue20341 messages
2014-01-22 10:31:28serhiy.storchakacreate