From 4d836989720523cd0363927e3e066f56b9dc445c Mon Sep 17 00:00:00 2001 From: yum Date: Sat, 17 Dec 2022 17:26:16 -0800 Subject: Check in `future` package I hit some issues installing Whisper and had to embed this package. I haven't taken the time to deeply understand what's going on. I think that embedded Python follows different rules about resolving module paths than regular system Python. Basically, `future`'s setup.py has a line like `import src`, where `src` is a module inside future (like `future/src/__init__.py`). This doesn't work unless we put that directory on the search path. --- .../future-0.18.2/docs/bind_method.rst | 29 ++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 Python/Dependencies/future-0.18.2/docs/bind_method.rst (limited to 'Python/Dependencies/future-0.18.2/docs/bind_method.rst') diff --git a/Python/Dependencies/future-0.18.2/docs/bind_method.rst b/Python/Dependencies/future-0.18.2/docs/bind_method.rst new file mode 100644 index 0000000..d737384 --- /dev/null +++ b/Python/Dependencies/future-0.18.2/docs/bind_method.rst @@ -0,0 +1,29 @@ +.. _bind-method: + +Binding a method to a class +--------------------------- + +Python 2 draws a distinction between bound and unbound methods, whereas +in Python 3 this distinction is gone: unbound methods have been removed +from the language. To bind a method to a class compatibly across Python +3 and Python 2, you can use the :func:`bind_method` helper function:: + + from future.utils import bind_method + + class Greeter(object): + pass + + def greet(self, message): + print(message) + + bind_method(Greeter, 'greet', greet) + + g = Greeter() + g.greet('Hi!') + + +On Python 3, calling ``bind_method(cls, name, func)`` is equivalent to +calling ``setattr(cls, name, func)``. On Python 2 it is equivalent to:: + + import types + setattr(cls, name, types.MethodType(func, None, cls)) -- cgit v1.2.3