From 784d0c261c76535dc760bc8d76793d92f35c1513 Mon Sep 17 00:00:00 2001 From: Claude Paroz Date: Mon, 2 Jul 2012 10:16:42 +0200 Subject: [PATCH] Replaced 'return' by 'raise' in custom model field docs Thanks Simon Charette for noticing it. Refs #11162. --- docs/howto/custom-model-fields.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/howto/custom-model-fields.txt b/docs/howto/custom-model-fields.txt index 8b4c2303ab..706cc25129 100644 --- a/docs/howto/custom-model-fields.txt +++ b/docs/howto/custom-model-fields.txt @@ -440,7 +440,7 @@ database, so we need to be able to process strings and ``Hand`` instances in Notice that we always return a ``Hand`` instance from this method. That's the Python object type we want to store in the model's attribute. If anything is -going wrong during value conversion, you should return a +going wrong during value conversion, you should raise a :exc:`~django.core.exceptions.ValidationError` exception. **Remember:** If your custom field needs the :meth:`to_python` method to be