mirror of
https://github.com/davidhalter/typeshed.git
synced 2026-01-02 09:33:25 +08:00
Fix typos in docs and comments (#11064)
This commit is contained in:
@@ -119,7 +119,7 @@ webob.cachecontrol.UpdateDict.setdefault
|
||||
# These need to be ignored due to how WebOb decided to let people know
|
||||
# that certain methods on `NestedMultiDict` should not be called since
|
||||
# they are immutable, compared to a MultiDict, but still can be used
|
||||
# interchangeably in some parts of the API. So they re-use generic functions
|
||||
# interchangeably in some parts of the API. So they reuse generic functions
|
||||
# that accept any parameters and assign them to methods which should still
|
||||
# satisfy the same interface. The type annotations enforce the correct
|
||||
# input arguments instead of the generic ones.
|
||||
@@ -148,6 +148,6 @@ webob.multidict.NoVars.__bool__
|
||||
# so the type annotation is technically wrong, however I am unsure about
|
||||
# whether the ResponseBodyFile would satisfy some of the IO Protocols if
|
||||
# `write` was defined as a Callable instance attribute. It's hard to come up
|
||||
# with a use-case where the distinction matters, besides inherting from
|
||||
# with a use-case where the distinction matters, besides inheriting from
|
||||
# the class and overwriting the __init__ and forgetting to populate `write`.
|
||||
webob.response.ResponseBodyFile.write
|
||||
|
||||
@@ -13,7 +13,7 @@ from webob.response import Response
|
||||
_T = TypeVar("_T")
|
||||
# we accept both the official spelling and the one used in the WebOb docs
|
||||
# the implementation compares after lower() so technically there are more
|
||||
# valid spellings, but it seems mor natural to support these two spellings
|
||||
# valid spellings, but it seems more natural to support these two spellings
|
||||
_SameSitePolicy: TypeAlias = Literal["Strict", "Lax", "None", "strict", "lax", "none"]
|
||||
|
||||
class _Serializer(Protocol):
|
||||
|
||||
Reference in New Issue
Block a user