OAi,SrSSKJr SSKrSSKrSSKJr SSKJrJ r J r "SS\ 5r SSjr SS jr SS jrSS jr\ "S 5r\ "S 5rSSjrg)zLA peculiar method of monkeypatching C++ binding classes with Python methods.) annotationsN)Callable)AnyProtocolTypeVarc8\rSrSr%SrS\S'S\S'S SjrSrg) AugmentedCallablez0Protocol for any method, with attached booleans.bool_augment_override_cpp_augment_if_no_cppcg)z Any function.N)selfargskwargss M/var/www/html/land-ocr/venv/lib/python3.13/site-packages/pikepdf/_augments.py__call__AugmentedCallable.__call__srN)returnr)__name__ __module__ __qualname____firstlineno____doc____annotations__r__static_attributes__rrrr r s:rr cSUlU$)z0Replace the C++ implementation, if there is one.T)r fns raugment_override_cppr"s#B IrcSUlU$)z@Provide a Python implementation if no C++ implementation exists.T)r r s raugment_if_no_cppr$s B Irc8URRS5$)Nzobject.)r startswith)meths r_is_inherited_methodr($s    ' ' 22rc[R"U5=(a [U5(+=(d [R"U5$)N)inspect isfunctionr(isdatadescriptor)ms r_is_augmentabler.*s61=&:1&="= %  ! !! $%rTcppTcd^1Skm[R"5S:XaTS1-mU4SU4SjjjnU$)aAttach methods of a Python support class to an existing class. This monkeypatches all methods defined in the support class onto an existing class. Example: .. code-block:: python @augments(ClassDefinedInCpp) class SupportClass: def foo(self): pass The Python method 'foo' will be monkeypatched on ClassDefinedInCpp. SupportClass has no meaning on its own and should not be used, but gets returned from this function so IDE code inspection doesn't get too confused. We don't subclass because it's much more convenient to monkeypatch Python methods onto the existing Python binding of the C++ class. For one thing, this allows the implementation to be moved from Python to C++ or vice versa. It saves having to implement an intermediate Python subclass and then ensures that the C++ superclass never 'leaks' to pikepdf users. Finally, wrapper classes and subclasses can become problematic if the call stack crosses the C++/Python boundary multiple times. Any existing methods may be used, regardless of whether they are defined elsewhere in the support class or in the target class. For data fields to work, the target class must be tagged ``py::dynamic_attr`` in pybind11. Strictly, the target class does not have to be C++ or derived from pybind11. This works on pure Python classes too. THIS DOES NOT work for class methods. (Alternative ideas: https://github.com/pybind/pybind11/issues/1074) >__eq____hash____repr__PyPy __getattr__c:>[R"U[S9GHrup#US:XaM[X5(a[X5(aU[ US[ 55;anUT;ah[ [ X5SS5(dM[ [ X5SS5(aM[ SUSUS US [ XS 5<S [ XS 5<3 5e[R"U5(ax[X5(a[US U3[ X55 [XU5 [ X5nURRURUR5Ul GMH[R"U5(dGMf[XU5 GMu SnXPl U$)N) predicate __weakref____abstractmethods__r Fr zC++ z and Python z* both define the same non-abstract method z: z, _cppcF[URRS-5e)Nz .__init__)NotImplementedError __class__r)rs r disable_init5augments..class_augment..disable_inits%dnn&=&= &KL Lr)r* getmembersr.hasattrgetattrset RuntimeErrorr+setattrrreplacerr,__init__)clscls_cppnamememberinstalled_memberr@OVERRIDE_WHITELISTs r class_augmentaugments..class_augment_s{$..soNLD}$&&C&&-BCE JJ 22 24KUSS73-/CUKK #7)<u5++/&wb14Bs"-02 !!&))7))GtD6]GG4JKv.#*7#9 060C0C0K0KLL'"2"21 -))&11v.UOX M$  r)rJtype[T]rK type[Tcpp]rrR)platformpython_implementation)rKrPrOs @raugmentsrV4s@L<%%'61}o-:A55n r)r!r rr )r'rrr )r-rrr )rKrS)r __future__rr*rTcollections.abcrtypingrrrr r"r$r(r.r/r0rVrrrrZsWS"$))  3 % v CLbr