p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed another typo in custom model field documentation.

This commit is contained in:
Baptiste Mispelon 2013-12-05 23:11:30 +01:00
parent 3396d5716b
commit 38662d11c4
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/howto/custom-model-fields.txt
View File

@ -304,7 +304,7 @@ Pay extra attention if you set new default values for arguments in the
than disappearing if they take on the old default value. than disappearing if they take on the old default value.
In addition, try to avoid returning values as positional arguments; where In addition, try to avoid returning values as positional arguments; where
possible, return values as keyword arguments for maximum future compatability. possible, return values as keyword arguments for maximum future compatibility.
Of course, if you change the names of things more often than their position Of course, if you change the names of things more often than their position
in the constructor's argument list, you might prefer positional, but bear in in the constructor's argument list, you might prefer positional, but bear in
mind that people will be reconstructing your field from the serialized version mind that people will be reconstructing your field from the serialized version