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 larry
Recipients larry, serhiy.storchaka, zach.ware
Date 2015-04-12.14:00:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Saying that "str" is redundant makes me think you don't understand what "types" does.  "types" accepts a text string listing all of the Python types the converter accepts.  You can accept the converter's default, or you can specify your own value.  If you specify your own value you must list all the types.  So "str" is not redundant there.

The problem with "which one is more obvious": we could get rid of "nullable" and just use "types".  But we can't get rid of "types".  If we keep both, now we theoretically have two ways to specify it.  Which should you use?  Do we say "you must use the nullable parameter, you're not allowed to specify NoneType in types", and if so, why?

p.s. I promised to rename "nullable" to "accepts_none".  Obviously if I just get rid of it I needn't bother.

p.p.s. Should types accept a "+" to mean "all the defaults, and..."?  For example, calling str(types="+ foo") was equivalent to str(types="str foo")?
Date User Action Args
2015-04-12 14:00:58larrysetrecipients: + larry, zach.ware, serhiy.storchaka
2015-04-12 14:00:58larrysetmessageid: <>
2015-04-12 14:00:58larrylinkissue23920 messages
2015-04-12 14:00:57larrycreate