Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #43952
| Path | csiph.com!usenet.pasdenom.info!news.albasani.net!newsfeed.freenet.ag!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail |
|---|---|
| Return-Path | <kwpolska@gmail.com> |
| X-Original-To | python-list@python.org |
| Delivered-To | python-list@mail.python.org |
| X-Spam-Status | OK 0.017 |
| X-Spam-Evidence | '*H*': 0.97; '*S*': 0.00; 'string.': 0.05; 'json': 0.07; 'string': 0.09; 'converted': 0.09; 'parsed': 0.09; 'cc:addr :python-list': 0.11; 'delimit': 0.16; 'gpg': 0.16; 'nan': 0.16; 'sense,': 0.16; 'wayne': 0.16; 'wrote:': 0.18; 'value.': 0.19; 'proposed': 0.22; 'cc:addr:python.org': 0.22; 'string,': 0.24; 'unicode': 0.24; 'cc:2**0': 0.24; 'cc:no real name:2**0': 0.24; 'header:In-Reply-To:1': 0.27; 'point': 0.28; 'chris': 0.29; 'especially': 0.30; 'message-id:@mail.gmail.com': 0.30; 'asked': 0.31; 'object.': 0.31; 'proposing': 0.31; 'text': 0.33; 'fri,': 0.33; 'skip:? 10': 0.33; 'received:google.com': 0.35; 'url:org': 0.36; 'pm,': 0.38; 'most': 0.60; 'from:charset:utf-8': 0.61; 'back': 0.62; '21st': 0.68; 'ps.': 0.84; 'edwards': 0.91; 'to:none': 0.92; 'url:tk': 0.95; '2013': 0.98 |
| DKIM-Signature | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:cc:content-type; bh=oIHdTGnnnxa6H2BAeRxJmFLXAANXPFqwgYIDSkXxPQs=; b=GkCmVGHpkAwMjrxKzMas0MYeqFy7sIK/toiIENiyp1Av8MtACHiuvYjJB6ZBQNPuak QiYf9rjfSb0lsMBrFhOZWEaanr5I6oP2Lphgq5KgCUwI+xQ1X3jJsKxt1v11l/Ot+Q9N VZXZz2TtIYCRPbaqzwk6aG5Ru3EbNbK48tgCtwzCRuyKnc+9z57tTFmAgFOEu0xBuHVc VaVPWcLvTF8sR3kXYfKPi50sk7mkSo8L4RQFfFJ+U5MKe8jHl2B2lCYfeZv+nlkKB84k z6hyOcd5TswykdpbJooEmrKPmaxJBkV9nzdJ4APRJLzePE+V+00d/aBf55+qTgxNTFhT k7eQ== |
| X-Received | by 10.50.237.71 with SMTP id va7mr17385116igc.88.1366444843042; Sat, 20 Apr 2013 01:00:43 -0700 (PDT) |
| MIME-Version | 1.0 |
| In-Reply-To | <kks6np$mvt$1@reader1.panix.com> |
| References | <bf3bf709-9cca-4488-a3c7-97b066bb2adf@googlegroups.com> <k4dsm8dea0gi3gf689p94el7gc6b1vk4bh@4ax.com> <c37a3b9c-6fe8-48aa-b703-9b4f922c3969@googlegroups.com> <mailman.770.1366293244.3114.python-list@python.org> <kkrlr4$brs$1@reader1.panix.com> <mailman.836.1366395732.3114.python-list@python.org> <kks6np$mvt$1@reader1.panix.com> |
| From | Chris “Kwpolska” Warrick <kwpolska@gmail.com> |
| Date | Sat, 20 Apr 2013 10:00:22 +0200 |
| Subject | Re: Encoding NaN in JSON |
| Cc | python-list@python.org |
| Content-Type | text/plain; charset=UTF-8 |
| X-BeenThere | python-list@python.org |
| X-Mailman-Version | 2.1.15 |
| Precedence | list |
| List-Id | General discussion list for the Python programming language <python-list.python.org> |
| List-Unsubscribe | <http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe> |
| List-Archive | <http://mail.python.org/pipermail/python-list/> |
| List-Post | <mailto:python-list@python.org> |
| List-Help | <mailto:python-list-request@python.org?subject=help> |
| List-Subscribe | <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.850.1366445217.3114.python-list@python.org> (permalink) |
| Lines | 21 |
| NNTP-Posting-Host | 2001:888:2000:d::a6 |
| X-Trace | 1366445217 news.xs4all.nl 2260 [2001:888:2000:d::a6]:58178 |
| X-Complaints-To | abuse@xs4all.nl |
| Xref | csiph.com comp.lang.python:43952 |
Show key headers only | View raw
On Fri, Apr 19, 2013 at 9:42 PM, Grant Edwards <invalid@invalid.invalid> wrote: > The OP asked for a string, and I thought you were proposing the string > 'null'. If one is to use a string, then 'NaN' makes the most sense, > since it can be converted back into a floating point NaN object. > > I infer that you were proposing a JSON null value and not the string > 'null'? Not me, Wayne Werner proposed to use the JSON null value. I parsed the backticks (`) used by him as a way to delimit it from text and not as a string. PS. > On 2013-04-19, Chris ???Kwpolska??? Warrick <kwpolska@gmail.com> wrote: Is Unicode support so hard, especially in the 21st century? -- Kwpolska <http://kwpolska.tk> | GPG KEY: 5EAAEA16 stop html mail | always bottom-post http://asciiribbon.org | http://caliburn.nl/topposting.html
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Encoding NaN in JSON Miki Tebeka <miki.tebeka@gmail.com> - 2013-04-16 17:21 -0700
Re: Encoding NaN in JSON Tim Roberts <timr@probo.com> - 2013-04-16 22:38 -0700
Re: Encoding NaN in JSON Miki Tebeka <miki.tebeka@gmail.com> - 2013-04-17 07:33 -0700
Re: Encoding NaN in JSON John Gordon <gordon@panix.com> - 2013-04-17 14:47 +0000
Re: Encoding NaN in JSON Johann Hibschman <jhibschman@gmail.com> - 2013-04-17 14:05 -0500
Re: Encoding NaN in JSON Miki Tebeka <miki.tebeka@gmail.com> - 2013-04-17 14:21 -0700
Re: Encoding NaN in JSON Roland Koebler <r.koebler@yahoo.de> - 2013-04-18 00:40 +0200
Re: Encoding NaN in JSON Miki Tebeka <miki.tebeka@gmail.com> - 2013-04-17 18:01 -0700
Re: Encoding NaN in JSON Roland Koebler <r.koebler@yahoo.de> - 2013-04-18 03:39 +0200
Re: Encoding NaN in JSON Chris Angelico <rosuav@gmail.com> - 2013-04-18 11:41 +1000
Re: Encoding NaN in JSON Chris Angelico <rosuav@gmail.com> - 2013-04-18 11:46 +1000
Re: Encoding NaN in JSON Roland Koebler <r.koebler@yahoo.de> - 2013-04-18 10:11 +0200
Re: Encoding NaN in JSON Dave Angel <d@davea.name> - 2013-04-17 17:37 -0400
Re: Encoding NaN in JSON Wayne Werner <wayne@waynewerner.com> - 2013-04-18 08:53 -0500
Re: Encoding NaN in JSON Grant Edwards <invalid@invalid.invalid> - 2013-04-19 14:54 +0000
Re: Encoding NaN in JSON Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2013-04-19 20:21 +0200
Re: Encoding NaN in JSON Grant Edwards <invalid@invalid.invalid> - 2013-04-19 19:42 +0000
Re: Encoding NaN in JSON Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2013-04-20 10:00 +0200
Re: Encoding NaN in JSON Wayne Werner <wayne@waynewerner.com> - 2013-04-22 13:53 -0500
Re: Encoding NaN in JSON Tim Roberts <timr@probo.com> - 2013-04-18 22:04 -0700
Re: Encoding NaN in JSON Robert Kern <robert.kern@gmail.com> - 2013-04-19 11:43 +0530
Re: Encoding NaN in JSON Miki Tebeka <miki.tebeka@gmail.com> - 2013-04-19 12:52 -0700
csiph-web