Message 205114 - Python tracker

➜

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	mark.dickinson
Recipients	docs@python, mark.dickinson, picomancer, pitrou, serhiy.storchaka
Date	2013-12-03.12:32:59
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1386073979.52.0.652186486538.issue19871@psf.upfronthosting.co.za>
In-reply-to

Content
In context, the doc is correct: """ parse_float, if specified, will be called with the string of every JSON float to be decoded. By default, this is equivalent to float(num_str). """ IIUC, parse_float only comes into play once the JSON source has already been tokenized, and the tokenization stage has already rejected things like '.5' by that point. (The point of parse_float is that you can choose to turn numeric strings into decimal.Decimal instances instead of floats if you so wish.) I agree it could use clarification.

In context, the doc is correct:

"""
parse_float, if specified, will be called with the string of every JSON float to be decoded. By default, this is equivalent to float(num_str).
"""

IIUC, parse_float only comes into play once the JSON source has already been tokenized, and the tokenization stage has already rejected things like '.5' by that point.  (The point of parse_float is that you can choose to turn numeric strings into decimal.Decimal instances instead of floats if you so wish.)

I agree it could use clarification.

History
Date	User	Action	Args
2013-12-03 12:32:59	mark.dickinson	set	recipients: + mark.dickinson, pitrou, docs@python, serhiy.storchaka, picomancer
2013-12-03 12:32:59	mark.dickinson	set	messageid: <1386073979.52.0.652186486538.issue19871@psf.upfronthosting.co.za>
2013-12-03 12:32:59	mark.dickinson	link	issue19871 messages
2013-12-03 12:32:59	mark.dickinson	create