diff --git a/docs/howto/custom-management-commands.txt b/docs/howto/custom-management-commands.txt
index bfcea64..ae7127c 100644
a
|
b
|
look like this:
|
70 | 70 | output, you should write to ``self.stdout`` and ``self.stderr``, |
71 | 71 | instead of printing to ``stdout`` and ``stderr`` directly. By |
72 | 72 | using these proxies, it becomes much easier to test your custom |
73 | | command. |
| 73 | command. Note also that you don't need to end messages with a newline |
| 74 | character, it will be added automatically. |
74 | 75 | |
75 | 76 | The new custom command can be called using ``python manage.py closepoll |
76 | 77 | <poll_id>``. |
diff --git a/docs/releases/1.5.txt b/docs/releases/1.5.txt
index a5ce08a..d85ca00 100644
a
|
b
|
Django 1.5 also includes several smaller improvements worth noting:
|
253 | 253 | from :ref:`call_command <call-command>`. Any exception raised by the command |
254 | 254 | (mostly :ref:`CommandError <ref-command-exceptions>`) is propagated. |
255 | 255 | |
| 256 | Moreover, when you output errors or messages in your custom commands, you |
| 257 | should now use ``self.stdout.write('message')`` and |
| 258 | ``self.stderr.write('error')`` (newline will be added automatically). |
| 259 | |
256 | 260 | * The dumpdata management command outputs one row at a time, preventing |
257 | 261 | out-of-memory errors when dumping large datasets. |
258 | 262 | |