Skip to content

Commit 0c08b2e

Browse files
committed
tests : Simplify how to set up Python environment
Based on a feedback from Georgi Gerganov. Instead of setting up a virtual environment in Makefile, let users set up the Python environment. This is better since users may have their own preferred workflow/toolkit. Signed-off-by: Fujimoto Seiji <[email protected]>
1 parent de329b7 commit 0c08b2e

File tree

3 files changed

+10
-9
lines changed

3 files changed

+10
-9
lines changed

tests/librispeech/Makefile

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,6 @@ eval:
88
clean:
99
$(MAKE) -f eval.mk clean
1010

11-
setup-venv:
12-
python3 -m venv venv
13-
./venv/bin/pip install -r requirements.txt
14-
15-
clean-venv:
16-
rm -r venv
17-
1811
get-audio:
1912
wget -c $(TAR_URL)
2013
tar -xf test-clean.tar.gz

tests/librispeech/README.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,15 @@ performance of whisper.cpp on LibriSpeech corpus.
2929
3. Set up the environment to compute WER score.
3030

3131
```
32-
$ make setup-venv
32+
$ pip install -r requirements.txt
33+
```
34+
35+
For example, if you use `virtualenv`, you can set up it as follows:
36+
37+
```
38+
$ python3 -m venv venv
39+
$ . venv/bin/activate
40+
$ pip install -r requirements.txt
3341
```
3442

3543
4. Run the benchmark test.

tests/librispeech/eval.mk

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
PYTHON = ./venv/bin/python3
1+
PYTHON = python
22

33
WHISPER_PREFIX = ../../
44
WHISPER_MODEL = tiny

0 commit comments

Comments
 (0)