Skip to content

Fix mentioned Python versions to headline #333

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
corona10 merged 1 commit into from
May 11, 2024
Merged

Fix mentioned Python versions to headline #333

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions doc/usage.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,11 +51,11 @@ Run benchmarks
Commands to compare Python 3.6 and Python 3.7 performance::

pyperformance run --python=python3.6 -o py36.json
pyperformance run --python=python3.7 -o py38.json
pyperformance compare py36.json py38.json
pyperformance run --python=python3.7 -o py37.json
pyperformance compare py36.json py37.json

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

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

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

python3 -m pyperf compare_to py36.json py38.json --table
python3 -m pyperf compare_to py36.json py37.json --table

Basic commands
--------------
Expand Down