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/src/libfuturize/fixes/fix_division.py | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 Python/Dependencies/future-0.18.2/src/libfuturize/fixes/fix_division.py (limited to 'Python/Dependencies/future-0.18.2/src/libfuturize/fixes/fix_division.py') diff --git a/Python/Dependencies/future-0.18.2/src/libfuturize/fixes/fix_division.py b/Python/Dependencies/future-0.18.2/src/libfuturize/fixes/fix_division.py new file mode 100644 index 0000000..6975a52 --- /dev/null +++ b/Python/Dependencies/future-0.18.2/src/libfuturize/fixes/fix_division.py @@ -0,0 +1,12 @@ +""" +UNFINISHED +For the ``future`` package. + +Adds this import line: + + from __future__ import division + +at the top so the code runs identically on Py3 and Py2.6/2.7 +""" + +from libpasteurize.fixes.fix_division import FixDivision -- cgit v1.2.3