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. --- Python/Dependencies/future-0.18.2/docs/metaclasses.rst | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 Python/Dependencies/future-0.18.2/docs/metaclasses.rst (limited to 'Python/Dependencies/future-0.18.2/docs/metaclasses.rst') diff --git a/Python/Dependencies/future-0.18.2/docs/metaclasses.rst b/Python/Dependencies/future-0.18.2/docs/metaclasses.rst new file mode 100644 index 0000000..d40c5a4 --- /dev/null +++ b/Python/Dependencies/future-0.18.2/docs/metaclasses.rst @@ -0,0 +1,18 @@ +Metaclasses +----------- + +Python 3 and Python 2 syntax for metaclasses are incompatible. +``future`` provides a function (from ``jinja2/_compat.py``) called +:func:`with_metaclass` that can assist with specifying metaclasses +portably across Py3 and Py2. Use it like this:: + + from future.utils import with_metaclass + + class BaseForm(object): + pass + + class FormType(type): + pass + + class Form(with_metaclass(FormType, BaseForm)): + pass -- cgit v1.2.3