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 Yury.Selivanov
Recipients Yury.Selivanov, doerwalter, larry, lemburg, ncoghlan, serhiy.storchaka, yselivanov
Date 2015-08-08.19:10:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <D01561FE-DF89-41E0-86DB-7E993FCD66A3@gmail.com>
In-reply-to <1439058451.96.0.672170719261.issue24824@psf.upfronthosting.co.za>
Content
> Can we do better?  How about a new field on the Parameter object, "symbolic_default_value", which shows you the expression used to compute the value?  We could then set default_value to the result of the expression, pydoc could print the symbolic expression, and codecs encode/decode could be more straightforward.

Maybe it's a good idea, but I'm -1 on pushing new APIs to 3.5 without some careful consideration at this super late stage (and it's not going to be a small change btw).

Let's just fix the codecs module.
History
Date User Action Args
2015-08-08 19:10:47Yury.Selivanovsetrecipients: + Yury.Selivanov, lemburg, doerwalter, ncoghlan, larry, serhiy.storchaka, yselivanov
2015-08-08 19:10:47Yury.Selivanovlinkissue24824 messages
2015-08-08 19:10:47Yury.Selivanovcreate