id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
25541	Improve error reporting when loading invalid JSON fixtures	awol	nobody	"We load a lot of data from fixtures that we generate from a CSV based data source. The transformation from CSV to JSON for the fixture is mostly fine but from time to time as the model changes or someone adds a different instance of the CSV data set, the fixture that gets created will fail to load for one reason or another. It is very hard/impossible to know which ""line"" in the fixture caused the exception that prevents the whole fixture from loading.

I am not sure what the most appropriate Django like fix for this issue is, however I have found that the following change is very successful at helping me find the appropriate place in the fixture JSON file and would appreciate if something along these lines would be available in the project.

{{{
django/core/serializers/json.py	2015-10-11 22:30:32.590127937 +1100
***************
*** 82,87 ****
--- 82,88 ----
          raise
      except Exception as e:
          # Map to deserializer error
+        e.message += "" Last success '{}: {}'."".format(obj.object.__class__.__name__, obj.object)
          six.reraise(DeserializationError, DeserializationError(e), sys.exc_info()[2])
}}}
"	Cleanup/optimization	new	Core (Serialization)	1.8	Normal		JSON fixture error		Accepted	0	0	0	0	0	0