Make "coerce" of fast_real apply to both string and numeric input #5
Comments
SethMMorton
added a commit
that referenced
this issue
Apr 23, 2016
The fast_real option coerce now applies to string input as well, so that users can control behavior better. The default is True which is opposite of the previous behavior. This should not be too much of a hit to backwards compatibility. This closes issue #5.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, if a string with an int-like float (i.e.
'4.0') is given tofast_real, it will be returned as anintinstead of afloat. The user has the option to toggle this behavior for numeric input with thecoerceoption.I will make the
coerceoption apply to both string and numeric input, and change the default toTrue; the default is currentlyFalse, but since it only applies to numbers currently and the option was only recently added I feel like making itTruewill be the least invasive for backwards-compatibility purposes.The text was updated successfully, but these errors were encountered: