Message87155
> Wouldn't it make more sense to switch to type 's',
> with a precision of 0, so as to use the same logic that float_str
uses?
Yes, that makes some sense. How would you handle
'{:.10}'.format(10/3.), though? We could either change 's' to allow a
precision, or use 's' when there's no precision specified and 'g' (with
the ADD_DOT_0 flag) otherwise.
> Or, also switch float_str to use 'g' with a precision of
> PyFloat_STR_PRECISION, and get rid of 's' altogether.
This sounds good to me. It does feel as though there's unnecessary
duplication with the current setup. |
|
Date |
User |
Action |
Args |
2009-05-04 19:30:16 | mark.dickinson | set | recipients:
+ mark.dickinson, eric.smith |
2009-05-04 19:30:16 | mark.dickinson | set | messageid: <1241465416.76.0.973930264117.issue5920@psf.upfronthosting.co.za> |
2009-05-04 19:30:15 | mark.dickinson | link | issue5920 messages |
2009-05-04 19:30:15 | mark.dickinson | create | |
|