blocks|key|2944901|text|您正在对JSON字符串进行双重编码。data已经了一个JSON字符串，不需要重新编码|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|2944902|>>>+import+json
>>>+not_encoded+=+{"created_at":"Fri+Aug+08+11:04:40+%2B0000+2014"}
>>>+encoded_data+=+json.dumps(not_encoded)
>>>+print+encoded_data
{"created_at":+"Fri+Aug+08+11:04:40+%2B0000+2014"}
>>>+double_encode+=+json.dumps(encoded_data)
>>>+print+double_encode
"{\"created_at\":+\"Fri+Aug+08+11:04:40+%2B0000+2014\"}"|code-block|syntax|javascript|2944903|只需将这些内容直接写入您的文件：|2944904|with+open('data{}.txt'.format(self.timestamp),+'a')+as+f:
++++f.write(data+%2B+'\n')|2944905|entityMap^0|I|4|O|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|D]]|E|@]|F|$]]|$1|G|3|H|5|I|7|W|8|@]|E|@]|F|$J|K]]|$1|L|3|M|5|6|7|X|8|@]|E|@]|F|$]]|$1|N|3|O|5|I|7|Y|8|@]|E|@]|F|$J|K]]|$1|P|3|-4|5|6|7|Z|8|@]|E|@]|F|$]]]|Q|$]]

You are double encoding your JSON strings. <code>data</code> is already a JSON string, and doesn't need to be encoded again:

<pre><code>&gt;&gt;&gt; import json
&gt;&gt;&gt; not_encoded = {"created_at":"Fri Aug 08 11:04:40 +0000 2014"}
&gt;&gt;&gt; encoded_data = json.dumps(not_encoded)
&gt;&gt;&gt; print encoded_data
{"created_at": "Fri Aug 08 11:04:40 +0000 2014"}
&gt;&gt;&gt; double_encode = json.dumps(encoded_data)
&gt;&gt;&gt; print double_encode
"{\"created_at\": \"Fri Aug 08 11:04:40 +0000 2014\"}"
</code></pre>

Just write these directly to your file:

<pre><code>with open('data{}.txt'.format(self.timestamp), 'a') as f:
 f.write(data + '\n')
</code></pre>

blocks|key|2732434|text|发生这种不想要的转义的另一种情况是，如果您尝试对json.dumps()的预处理输出使用json.dump()。例如|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2732435|import+json,+sys
json.dump({"foo":+json.dumps([{"bar":+1},+{"baz":+2}])},sys.stdout)|code-block|syntax|javascript|2732436|将导致|2732437|{"foo":+"[{\"bar\":+1},+{\"baz\":+2}]"}|2732438|为了避免这种情况，您需要传递字典而不是json.dumps()的输出，例如|2732439|json.dump({"foo":+[{"bar":+1},+{"baz":+2}]},sys.stdout)|2732440|它输出所需的|2732441|{"foo":+[{"bar":+1},+{"baz":+2}]}|2732442|(您会问，为什么要用json.dumps()对内部列表进行预处理？嗯，我有另一个函数，它从其他东西中创建内部列表，我认为从该函数返回一个json对象是有意义的……错误。)|2732443|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|14|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

Another situation where this unwanted escaping can happen is if you try to use json.dump() on the pre-processed output of json.dumps(). For example

<pre><code>import json, sys
json.dump({"foo": json.dumps([{"bar": 1}, {"baz": 2}])},sys.stdout)
</code></pre>

will result in

<pre><code>{"foo": "[{\"bar\": 1}, {\"baz\": 2}]"}
</code></pre>

To avoid this, you need to pass dictionaries rather than the output of json.dumps(), e.g.

<pre><code>json.dump({"foo": [{"bar": 1}, {"baz": 2}]},sys.stdout)
</code></pre>

which outputs the desired

<pre><code>{"foo": [{"bar": 1}, {"baz": 2}]}
</code></pre>

(Why would you pre-process the inner list with json.dumps(), you ask? Well, I had another function that was creating that inner list out of other stuff, and I thought it would make sense to return a json object from that function... Wrong.)

blocks|key|148644|text|对于其他有类似问题的人，我用它将JSON格式的数据转储到文件中，其中的数据来自API调用。下面只是一个指示性的例子，请根据您的需求进行更新|type|unstyled|depth|inlineStyleRanges|entityRanges|data|148645|import+json

#+below+is+an+example,+this+came+for+me+from+an+API+call
json_string+=+'{"address":{"city":"NY",+"country":"USA"}}'

#+dump+the+JSON+data+into+file+(+dont+use+json.dump+as+explained+in+other+answers+)
with+open('direct_json.json','w')+as+direct_json:++++
++++direct_json.write(json_string)
++++direct_json.write("\n")

#+load+as+dict
json_dict+=+json.loads(json_string)

#+pretty+print
print(json.dumps(json_dict,+indent+=+1))+

#+write+pretty+JSON+to+file
with+open('formatted.json','w')+as+formatted_file:+
++++json.dump(json_dict,+formatted_file,+indent=4)++|code-block|syntax|javascript|148646|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Extending for others having similar issue, I used this to dump the JSON formatted data to file where the data came from an API call. Just an indicative example below, update as per your requirement
<pre><code>import json

# below is an example, this came for me from an API call
json_string = '{&quot;address&quot;:{&quot;city&quot;:&quot;NY&quot;, &quot;country&quot;:&quot;USA&quot;}}'

# dump the JSON data into file ( dont use json.dump as explained in other answers )
with open('direct_json.json','w') as direct_json: 
 direct_json.write(json_string)
 direct_json.write(&quot;\n&quot;)

# load as dict
json_dict = json.loads(json_string)

# pretty print
print(json.dumps(json_dict, indent = 1)) 

# write pretty JSON to file
with open('formatted.json','w') as formatted_file: 
 json.dump(json_dict, formatted_file, indent=4) 
</code></pre>

blocks|key|2944975|text|解决这个问题的简单方法是在转储之前使用json+loads函数，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2944976|import+json
data+=+json.loads('{"foo":+json.dumps([{"bar":+1},+{"baz":+2}])}')
with+open('output.json','w')+as+f:
+++json.dump(data,f,indent=4)|code-block|syntax|javascript|2944977|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Simple way to get around that, which worked for me is to use the json loads function before dumping, like the following :
<pre class="lang-py prettyprint-override"><code>import json
data = json.loads('{&quot;foo&quot;: json.dumps([{&quot;bar&quot;: 1}, {&quot;baz&quot;: 2}])}')
with open('output.json','w') as f:
 json.dump(data,f,indent=4)

</code></pre>

I am retrieving Twitter data with a Python tool and dump these in JSON format to my disk. I noticed an unintended escaping of the entire data-string for a tweet being enclosed in double quotes. Furthermore, all double quotes of the actual JSON formatting are escaped with a backslash.

They look like this:

<blockquote>
 "{\"created_at\":\"Fri Aug 08 11:04:40 +0000
 2014\",\"id\":497699913925292032,
</blockquote>

How do I avoid that? It should be:

<blockquote>
 {"created_at":"Fri Aug 08 11:04:40 +0000 2014" .....
</blockquote>

My file-out code looks like this:

<pre><code>with io.open('data'+self.timestamp+'.txt', 'a', encoding='utf-8') as f:
 f.write(unicode(json.dumps(data, ensure_ascii=False)))
 f.write(unicode('\n'))
</code></pre>

The unintended escaping causes problems when reading in the JSON file in a later processing step.

Dump to JSON adds additional double quotes and escaping of quotes

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我使用Python工具检索Twitter数据，并将这些数据以JSON格式转储到我的磁盘上。我注意到一个用双引号括起来的tweet的整个数据字符串的意外转义。此外，实际JSON格式的所有双引号都使用反斜杠进行转义。它们看起来像这样： "{\"created_at\":\"Fri Aug 08 11:04:40 +0000...

问Dump to JSON添加了额外的双引号和转义引号
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Dump to JSON添加了额外的双引号和转义引号EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Dump to JSON添加了额外的双引号和转义引号
EN