Cleanup: prefer 'arg' over 'params' for sphinx documentation
While both are supported, 'arg' is in more common use so prefer it.
This commit is contained in:
@@ -63,15 +63,15 @@ PyDoc_STRVAR(
|
||||
"\n"
|
||||
" Add a new attribute to the format.\n"
|
||||
"\n"
|
||||
" :param id: Name the attribute. Often `position`, `normal`, ...\n"
|
||||
" :arg id: Name the attribute. Often `position`, `normal`, ...\n"
|
||||
" :type id: str\n"
|
||||
" :param comp_type: The data type that will be used store the value in memory.\n"
|
||||
" :arg comp_type: The data type that will be used store the value in memory.\n"
|
||||
" Possible values are `I8`, `U8`, `I16`, `U16`, `I32`, `U32`, `F32` and `I10`.\n"
|
||||
" :type comp_type: str\n"
|
||||
" :param len: How many individual values the attribute consists of\n"
|
||||
" :arg len: How many individual values the attribute consists of\n"
|
||||
" (e.g. 2 for uv coordinates).\n"
|
||||
" :type len: int\n"
|
||||
" :param fetch_mode: How values from memory will be converted when used in the shader.\n"
|
||||
" :arg fetch_mode: How values from memory will be converted when used in the shader.\n"
|
||||
" This is mainly useful for memory optimizations when you want to store values with\n"
|
||||
" reduced precision. E.g. you can store a float in only 1 byte but it will be\n"
|
||||
" converted to a normal 4 byte float when used.\n"
|
||||
|
||||
Reference in New Issue
Block a user