aboutsummaryrefslogtreecommitdiff
path: root/bindings/python-cffi
diff options
context:
space:
mode:
authorDavid Bremner <david@tethera.net>2025-02-22 13:42:49 -0400
committerDavid Bremner <david@tethera.net>2025-03-18 09:15:16 -0300
commiteaf3cd10db95b366c960a4f87e4a513dc9488e7f (patch)
treee54382821db88c5abfc4bcd71a252ad1dbfd0e2c /bindings/python-cffi
parent14f7a8929abedc465e30e8ec77c1bea72db35d9d (diff)
doc/python: correct wording around container complexity.
Based on a suggestion from Jakub Wilk.
Diffstat (limited to 'bindings/python-cffi')
-rw-r--r--bindings/python-cffi/notmuch2/__init__.py6
1 files changed, 3 insertions, 3 deletions
diff --git a/bindings/python-cffi/notmuch2/__init__.py b/bindings/python-cffi/notmuch2/__init__.py
index f281edc1..b1cd21c1 100644
--- a/bindings/python-cffi/notmuch2/__init__.py
+++ b/bindings/python-cffi/notmuch2/__init__.py
@@ -37,9 +37,9 @@ In these python bindings they have sometimes been exposed as
like :class:`collections.abc.Set` or :class:`collections.abc.Mapping`
etc. This gives a more natural API to work with, e.g. being able to
treat tags as sets. However it does mean that the
-:meth:`__contains__`, :meth:`__len__` and frieds methods on these are
-usually more and essentially O(n) rather than O(1) as you might
-usually expect from Python containers.
+:meth:`__contains__`, :meth:`__len__` and similar methods on these are
+usually more expensive and essentially O(n) rather than O(1) as you might
+expect from Python containers.
"""
from notmuch2 import _capi