8000 Fix mentioned Python versions to headline (#333) · python/pyperformance@bce7b77 · GitHub
[go: up one dir, main page]

Skip to content

Commit bce7b77

Browse files
authored
Fix mentioned Python versions to headline (#333)
In the previous version, the document gave an example on how to compare Python 3.6 and Python 3.7 performance. However, the commands in the example referred partially to Python 3.8. Since this is confusing and not inline with the first line of the section, I changed the example so that it fits the text.
1 parent f451bb0 commit bce7b77

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

doc/usage.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -51,11 +51,11 @@ Run benchmarks
5151
Commands to compare Python 3.6 and Python 3.7 performance::
5252

5353
pyperformance run --python=python3.6 -o py36.json
54-
pyperformance run --python=python3.7 -o py38.json
55-
pyperformance compare py36.json py38.json
54+
pyperformance run --python=python3.7 -o py37.json
55+
pyperformance compare py36.json py37.json
5656

5757
Note: ``python3 -m pyperformance ...`` syntax works as well (ex: ``python3 -m
58-
pyperformance run -o py38.json``), but requires to install pyperformance on each
58+
pyperformance run -o py37.json``), but requires to install pyperformance on each
5959
tested Python version.
6060

6161
JSON files are produced by the pyperf module and so can be analyzed using pyperf
@@ -71,7 +71,7 @@ commands::
7171

7272
It's also possible to use pyperf to compare results of two JSON files::
7373

74-
python3 -m pyperf compare_to py36.json py38.json --table
74+
python3 -m pyperf compare_to py36.json py37.json --table
7575

7676
Basic commands
7777
--------------

0 commit comments

Comments
 (0)
0