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 ncoghlan
Recipients barry, gregory.p.smith, larry, ncoghlan, rhettinger, serhiy.storchaka, taleinat, zach.ware
Date 2015-05-08.23:05:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7fNLKD7T=vL21YOJhDcFz0asm6bNgs+nEEGsfNUXUkGTA@mail.gmail.com>
In-reply-to <1431090041.48.0.549666594591.issue24145@psf.upfronthosting.co.za>
Content
Aye, it occurs to me now that introducing the implicit form trades a "write
time" lookup (where you have to override the converter defaults
explicitly), for a "read time" lookup (where you need to mentally add the
defaults to understand the modified accept clause)

As a result, I think "explicit is better than implicit" wins, at least for
now. If we decide after we have more experience that the repetition of the
defaults when overriding them really is a problem, then it's possible to
revisit that decision in the 3.6 time frame.
History
Date User Action Args
2015-05-08 23:05:42ncoghlansetrecipients: + ncoghlan, barry, rhettinger, gregory.p.smith, taleinat, larry, zach.ware, serhiy.storchaka
2015-05-08 23:05:42ncoghlanlinkissue24145 messages
2015-05-08 23:05:42ncoghlancreate