Change by Kevin Mills :
--
nosy: +Zeturic
___
Python tracker
<https://bugs.python.org/issue43574>
___
___
Python-bugs-list mailing list
Unsubscribe:
Kevin Mills added the comment:
Sorry to the people I'm pinging, but I just noticed the initial dictionary in
my example code is wrong. I figured I should fix it before anybody tested it
and got confused about it not matching up with my description of the results.
It should've bee
New submission from Kevin Mills :
The json module will allow the following without complaint:
import json
d1 = {1: "fromstring", "1": "fromnumber"}
string = json.dumps(d1)
print(string)
d2 = json.loads(string)
print(d2)
And it prints:
{"1": "from
New submission from Kevin Mills :
Sorry for the vague title. I'm not sure how to succinctly describe this issue.
The following code:
```
with open("data.bin", "rb") as f:
data = f.read()
base = 15403807 * b'\xff'
longer = base + b'\xff'
Kevin Mills added the comment:
gc.disable() at the beginning and then analyzing the results of gc.collect()
actually does do what I was wanting, thank you.
Reference cycles in and of themselves aren't the problem. It's only a problem
if garbage contains reference cycles. In a norm
New submission from Kevin Mills:
The intro paragraph for the gc module's documentation says:
> Since the collector supplements the reference counting already used in
> Python, you can disable the collector if you are sure your program does not
> create reference cycles.
How wou
