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/futurize.py | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 Python/Dependencies/future-0.18.2/futurize.py (limited to 'Python/Dependencies/future-0.18.2/futurize.py') diff --git a/Python/Dependencies/future-0.18.2/futurize.py b/Python/Dependencies/future-0.18.2/futurize.py new file mode 100644 index 0000000..cb446ab --- /dev/null +++ b/Python/Dependencies/future-0.18.2/futurize.py @@ -0,0 +1,24 @@ +#!/usr/bin/env python +""" +futurize.py +=========== + +This script is only used by the unit tests. Another script called +"futurize" is created automatically (without the .py extension) by +setuptools. + +futurize.py attempts to turn Py2 code into valid, clean Py3 code that is +also compatible with Py2 when using the ``future`` package. + + +Licensing +--------- +Copyright 2013-2019 Python Charmers Pty Ltd, Australia. +The software is distributed under an MIT licence. See LICENSE.txt. +""" + +import sys + +from libfuturize.main import main + +sys.exit(main()) -- cgit v1.2.3