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/hindsight.rst | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 Python/Dependencies/future-0.18.2/docs/hindsight.rst (limited to 'Python/Dependencies/future-0.18.2/docs/hindsight.rst') diff --git a/Python/Dependencies/future-0.18.2/docs/hindsight.rst b/Python/Dependencies/future-0.18.2/docs/hindsight.rst new file mode 100644 index 0000000..b4654c6 --- /dev/null +++ b/Python/Dependencies/future-0.18.2/docs/hindsight.rst @@ -0,0 +1,3 @@ +In a perfect world, the new metaclass syntax should ideally be available in +Python 2 as a `__future__`` import like ``from __future__ import +new_metaclass_syntax``. -- cgit v1.2.3