Message191633
| Author |
gvanrossum |
| Recipients |
amaury.forgeotdarc, barry, eli.bendersky, eric.snow, ethan.furman, ezio.melotti, gvanrossum, ncoghlan, pitrou, rhettinger |
| Date |
2013年06月22日.04:55:33 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAP7+vJ+1buCoXURuAg+kSNYv7m23Q8i8d_vw9stzkA+krVOcQw@mail.gmail.com> |
| In-reply-to |
<51C518AD.4000900@stoneleaf.us> |
| Content |
Yes for float() -- but for str() it would seem redundant? (Or what's
the context?)
On Fri, Jun 21, 2013 at 8:23 PM, Ethan Furman <report@bugs.python.org> wrote:
>
> Ethan Furman added the comment:
>
> On 06/21/2013 07:49 PM, Guido van Rossum wrote:
>> Eli Bendersky added the comment:
>>>
>>> Practically speaking, what should be done to make enum play well with JSON
>>> without writing new PEPs? I think we still want to convert those stdlib
>>> constants to IntEnums...
>>
>> Change json to call int() first.
>
> Should we have json call float() and str() first as well? I'm thinking less of the stdlib and more of the unsuspecting
> user.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue18264>
> _______________________________________ |
|