Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #95724
| From | Jussi Piitulainen <harvestingn@makes.address.invalid> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: Casting to a "number" (both int and float)? |
| Date | 2015-08-28 09:03 +0300 |
| Organization | A noiseless patient Spider |
| Message-ID | <lf51teokl0p.fsf@ling.helsinki.fi> (permalink) |
| References | <0bdda01a-de29-4742-9851-0617dad602ae@googlegroups.com> <mailman.96.1440740667.11709.python-list@python.org> |
Ben Finney writes:
> Victor Hooi writes:
>
>> Many of the fields are meant to be numerical, however, some fields are
>> wrapped in a "floatApprox" dict, which messed with my parsing.
>
> The examples you give of ‘floatApprox’ are not dicts, so I'm not sure
> quite what that means.
I took the distinction to be between 123123 and {"floatApprox":
213123123}. The former looks like an int, the latter like a dict.
>> "network": {
>> "bytesIn": 123123,
>> "bytesOut": {
>> "floatApprox": 213123123
>> }
> What do you mean by “wrapping”?
I read it so that the bytesOut value, 213123123, is "wrapped" in
{"floatApprox": }, and Victor wants just the number inside.
[- -]
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Casting to a "number" (both int and float)? Victor Hooi <victorhooi@gmail.com> - 2015-08-27 21:57 -0700
Re: Casting to a "number" (both int and float)? Victor Hooi <victorhooi@gmail.com> - 2015-08-27 22:04 -0700
Re: Casting to a "number" (both int and float)? "Sven R. Kunze" <srkunze@mail.de> - 2015-08-28 18:09 +0200
Re: Casting to a "number" (both int and float)? Robin Koch <robin.koch@t-online.de> - 2015-08-28 18:15 +0200
Re: Casting to a "number" (both int and float)? "Sven R. Kunze" <srkunze@mail.de> - 2015-08-30 13:38 +0200
Re: Casting to a "number" (both int and float)? Steven D'Aprano <steve@pearwood.info> - 2015-08-30 22:00 +1000
Re: Casting to a "number" (both int and float)? Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-08-30 13:55 +0100
Re: Casting to a "number" (both int and float)? Ben Finney <ben+python@benfinney.id.au> - 2015-08-28 15:44 +1000
Re: Casting to a "number" (both int and float)? Jussi Piitulainen <harvestingn@makes.address.invalid> - 2015-08-28 09:03 +0300
Re: Casting to a "number" (both int and float)? Jussi Piitulainen <harvesting@makes.address.invalid> - 2015-08-28 09:15 +0300
Re: Casting to a "number" (both int and float)? Victor Hooi <victorhooi@gmail.com> - 2015-08-28 00:56 -0700
Re: Casting to a "number" (both int and float)? Chris Angelico <rosuav@gmail.com> - 2015-08-28 19:23 +1000
Re: Casting to a "number" (both int and float)? Jussi Piitulainen <harvesting@makes.address.invalid> - 2015-08-28 08:46 +0300
Re: Casting to a "number" (both int and float)? random832@fastmail.us - 2015-08-28 01:54 -0400
Re: Casting to a "number" (both int and float)? Laura Creighton <lac@openend.se> - 2015-08-28 07:59 +0200
csiph-web