I'm glad that you've got it licked.
On Thu, May 30, 2013 at 4:36 PM, Gitonga Mbaya wrote:
> Ah, a bit of digging found the solution. This link explains the issue:
> http://bit.ly/13mS8ZB specifically:
>
> "cmd.exe" supports an ascii and an utf16 output mode: this can be selected
> by
> "cmd
Ah, a bit of digging found the solution. This link explains the
issue: http://bit.ly/13mS8ZB specifically:
"cmd.exe" supports an ascii and an utf16 output mode: this can be selected
by
"cmd.exe"-> ascii mode
"cmd.exe /u" -> unicode mode
The only difference between the two modes is th
What you say makes sense. I was just thinking about that very thing of the
nul character as I looked at the bad file in the hexeditor. I think your
suspicion of cmd.exe's ">" operation being at fault is the root of my
problems since the file is bad right from get go. Thanks much for all your
a
If all else fails this untested tool (attached) might translate bad files
to good ones. Run it like this:
python utr16toascii.py bad_file name_for_new_good_file
On Thu, May 30, 2013 at 4:10 PM, Bill Freeman wrote:
> This file is encoded in UTF-16 with a byte order mark. That is to say,
> o
This file is encoded in UTF-16 with a byte order mark. That is to say,
other than starting with \xff\xfe (the two character byte order mark),,
every other character is nul (\x00). There are actually 1449 useful
characters in this 2900 byte file. A converted version is attached.
json.load() is ha
I just did a fresh dump and I realise the difference is not that drastic.
The extra stuff must come from trying to edit it. Here is a fresh file from
the dump...
On Thursday, May 30, 2013 9:50:26 PM UTC+3, ke1g wrote:
>
> Can you load the file using json.load()? I.e.; is that one of the things
Can you load the file using json.load()? I.e.; is that one of the things
that you have already tried?
On Thu, May 30, 2013 at 2:32 PM, Gitonga Mbaya wrote:
> All you suggest I had already tried. Without indent, same result. dumping
> an xml file, same thing. The only thing I didn't try was loa
All you suggest I had already tried. Without indent, same result. dumping
an xml file, same thing. The only thing I didn't try was loading it in a
different project.
I am doing all this on Windows 7 on the same machine.
On Thursday, May 30, 2013 8:57:42 PM UTC+3, ke1g wrote:
>
> Try again witho
Try again without the indent (just for grins).
Are the two systems on the same box, or did you have to transfer it over a
network, or via a flash drive, or the like?
If two boxes, is one Windows and the other not? (Line boundaries differ,
though I would hope that the json tools would be proof ag
Bill,
These are the exact steps I follow:
python manage.py dumpdata --indent=4 > fixtures/data.json
python manage.py loaddata fixtures/data.json
That is when I get:
DeserializationError: No JSON object could be decoded
I checked the json code using http://jsonlint.com/ and it was reported as
Bill,
This is are the exact steps I follow:
python manage.py dumpdata --indent=4 > fixtures/data.json
python manage.py loaddata fixtures/data.json
That is when I get:
DeserializationError: No JSON object could be decoded
I checked the json code using http://jsonlint.com/ and it was reported a
When you say "created from a dumpdata export", do you mean that the file
has been edited since the export?
If so, you have probably introduced a syntax error in the JSON.
See if you can find a JSON validator site on the web, or an editor or tool
that pretty prints the JSON to see if you can spot
I have searched high and low for a solution to this problem and nothing I
could find anywhere led to a solution. On a whim I decided to type out the
json file into notepad and save it as a different json file. I then tried
loading that and it worked. Next I just copy pasted the contents of the
have a look at file and see if it looks ok.
I find I have to dump a model at a time and load them back in a sensible
sequence.
Connected by MOTOBLUR™
-Original message-
From: Vincent Bastos
To: django-users@googlegroups.com
Sent: Sun, 04 Mar 2012, 08:40:07 AEDT
Subject: Importing data
14 matches
Mail list logo
