Show More
@@ -67,21 +67,16 version to use. | |||
|
67 | 67 | Using pip |
|
68 | 68 | --------- |
|
69 | 69 | |
|
70 | Users of `pip` can install the Rust extensions with the following command:: | |
|
71 | ||
|
72 | $ pip install mercurial \ | |
|
73 | --global-option \ | |
|
74 | --rust \ | |
|
75 | --no-use-pep517 \ | |
|
76 | --no-binary mercurial | |
|
70 | Users of `pip` can install the Rust extensions with the following commands:: | |
|
77 | 71 | |
|
78 | `--no-use-pep517` is here to tell `pip` to preserve backwards compatibility with | |
|
79 | the legacy `setup.py` system. Mercurial has not yet migrated its complex setup | |
|
80 | to the new system, so we still need this to add compiled extensions. | |
|
72 | $ pip cache remove mercurial | |
|
73 | $ pip install mercurial -v \ | |
|
74 | --config-settings --global-option=--rust \ | |
|
75 | --no-binary mercurial --force | |
|
81 | 76 | |
|
82 |
`--no-binary` |
|
|
83 |
missing rust support. This might take a couple |
|
|
84 | compiling everything. | |
|
77 | `pip cache remove` and `--no-binary` are there to tell pip to not use the | |
|
78 | pre-compiled wheels that are missing rust support. This might take a couple | |
|
79 | of minutes because you're compiling everything. | |
|
85 | 80 | |
|
86 | 81 | See the "Checking for Rust" section to see if the install succeeded. |
|
87 | 82 |
General Comments 0
You need to be logged in to leave comments.
Login now