Updating test output to be compatible with pylint 2.13 (couple of column numbers changed)

carlio · carlio · commit 7d74a88827ee · 2022-03-25T15:45:24.000+01:00
diff --git a/pylint_django/tests/input/func_model_does_not_use_unicode_py33.txt b/pylint_django/tests/input/func_model_does_not_use_unicode_py33.txt
@@ -1 +1 @@
-model-has-unicode:9:0:19:29:SomeModel:Found __unicode__ method on model (SomeModel). Python3 uses __str__.:UNDEFINED
+model-has-unicode:9:0:9:15:SomeModel:Found __unicode__ method on model (SomeModel). Python3 uses __str__.:UNDEFINED
diff --git a/pylint_django/tests/input/func_model_no_explicit_unicode_str_compat.txt b/pylint_django/tests/input/func_model_no_explicit_unicode_str_compat.txt
@@ -1 +1 @@
-model-no-explicit-unicode:18:0:19:8:SomeModel:Model does not explicitly define __unicode__ (SomeModel):UNDEFINED
+model-no-explicit-unicode:18:0:18:15:SomeModel:Model does not explicitly define __unicode__ (SomeModel):UNDEFINED

Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		`-model-has-unicode:9:0:19:29:SomeModel:Found __unicode__ method on model (SomeModel). Python3 uses __str__.:UNDEFINED`
	`1`	`+model-has-unicode:9:0:9:15:SomeModel:Found __unicode__ method on model (SomeModel). Python3 uses __str__.:UNDEFINED`
Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		`-model-no-explicit-unicode:18:0:19:8:SomeModel:Model does not explicitly define __unicode__ (SomeModel):UNDEFINED`
	`1`	`+model-no-explicit-unicode:18:0:18:15:SomeModel:Model does not explicitly define __unicode__ (SomeModel):UNDEFINED`