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. --- .../Dependencies/future-0.18.2/src/future/moves/copyreg.py | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 Python/Dependencies/future-0.18.2/src/future/moves/copyreg.py (limited to 'Python/Dependencies/future-0.18.2/src/future/moves/copyreg.py') diff --git a/Python/Dependencies/future-0.18.2/src/future/moves/copyreg.py b/Python/Dependencies/future-0.18.2/src/future/moves/copyreg.py new file mode 100644 index 0000000..9d08cdc --- /dev/null +++ b/Python/Dependencies/future-0.18.2/src/future/moves/copyreg.py @@ -0,0 +1,12 @@ +from __future__ import absolute_import +from future.utils import PY3 + +if PY3: + import copyreg, sys + # A "*" import uses Python 3's copyreg.__all__ which does not include + # all public names in the API surface for copyreg, this avoids that + # problem by just making our module _be_ a reference to the actual module. + sys.modules['future.moves.copyreg'] = copyreg +else: + __future_module__ = True + from copy_reg import * -- cgit v1.2.3