Fix style to Keyword Args
This commit is contained in:
parent
fcb6f19287
commit
b449ebe3d4
55 changed files with 157 additions and 157 deletions
|
|
@ -1103,7 +1103,7 @@ class AttributeHandler:
|
|||
- `(key, value, category, lockstring)`
|
||||
- `(key, value, category, lockstring, default_access)`
|
||||
|
||||
Keyword args:
|
||||
Keyword Args:
|
||||
strattr (bool): If `True`, value must be a string. This
|
||||
will save the value without pickling which is less
|
||||
flexible but faster to search (not often used except
|
||||
|
|
|
|||
|
|
@ -258,7 +258,7 @@ class TypedObjectManager(idmapper.manager.SharedMemoryManager):
|
|||
this is either `None` (a normal Tag), `alias` or
|
||||
`permission`. This always apply to all queried tags.
|
||||
|
||||
Keyword args:
|
||||
Keyword Args:
|
||||
match (str): "all" (default) or "any"; determines whether the
|
||||
target object must be tagged with ALL of the provided
|
||||
tags/categories or ANY single one. ANY will perform a weighted
|
||||
|
|
@ -649,7 +649,7 @@ class TypeclassManager(TypedObjectManager):
|
|||
Args:
|
||||
args (any): These are passed on as arguments to the default
|
||||
django get method.
|
||||
Keyword args:
|
||||
Keyword Args:
|
||||
kwargs (any): These are passed on as normal arguments
|
||||
to the default django get method
|
||||
Returns:
|
||||
|
|
@ -671,7 +671,7 @@ class TypeclassManager(TypedObjectManager):
|
|||
Args:
|
||||
args (any): These are passed on as arguments to the default
|
||||
django filter method.
|
||||
Keyword args:
|
||||
Keyword Args:
|
||||
kwargs (any): These are passed on as normal arguments
|
||||
to the default django filter method.
|
||||
Returns:
|
||||
|
|
@ -794,7 +794,7 @@ class TypeclassManager(TypedObjectManager):
|
|||
Variation of get that not only returns the current typeclass
|
||||
but also all subclasses of that typeclass.
|
||||
|
||||
Keyword args:
|
||||
Keyword Args:
|
||||
kwargs (any): These are passed on as normal arguments
|
||||
to the default django get method.
|
||||
Returns:
|
||||
|
|
@ -819,7 +819,7 @@ class TypeclassManager(TypedObjectManager):
|
|||
Args:
|
||||
args (any): These are passed on as arguments to the default
|
||||
django filter method.
|
||||
Keyword args:
|
||||
Keyword Args:
|
||||
kwargs (any): These are passed on as normal arguments
|
||||
to the default django filter method.
|
||||
Returns:
|
||||
|
|
|
|||
|
|
@ -291,7 +291,7 @@ class TypedObject(SharedMemoryModel):
|
|||
Args:
|
||||
Passed through to parent.
|
||||
|
||||
Keyword args:
|
||||
Keyword Args:
|
||||
Passed through to parent.
|
||||
|
||||
Notes:
|
||||
|
|
@ -615,7 +615,7 @@ class TypedObject(SharedMemoryModel):
|
|||
no_superuser_bypass (bool, optional): Turn off the
|
||||
superuser lock bypass (be careful with this one).
|
||||
|
||||
Keyword args:
|
||||
Keyword Args:
|
||||
kwar (any): Ignored, but is there to make the api
|
||||
consistent with the object-typeclass method access, which
|
||||
use it to feed to its hook methods.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue