@@ -54,85 +54,85 @@ async def install(
54
54
55
55
Parameters
56
56
----------
57
- requirements :
57
+ requirements:
58
58
59
59
A requirement or list of requirements to install. Each requirement is a
60
60
string, which should be either a package name or a wheel URI:
61
61
62
- - If the requirement does not end in ``.whl``, it will be interpreted as
63
- a package name. A package with this name must either be present
62
+ - If the requirement does not end in ``.whl``, it will be interpreted as \
63
+ a package name. A package with this name must either be present \
64
64
in the Pyodide lock file or on PyPI.
65
65
66
- - If the requirement ends in ``.whl``, it is a wheel URI. The part of
67
- the requirement after the last ``/`` must be a valid wheel name in
68
- compliance with the `PEP 427 naming convention
66
+ - If the requirement ends in ``.whl``, it is a wheel URI. The part of \
67
+ the requirement after the last ``/`` must be a valid wheel name in \
68
+ compliance with the `PEP 427 naming convention \
69
69
<https://www.python.org/dev/peps/pep-0427/#file-format>`_.
70
70
71
- - If a wheel URI starts with ``emfs:``, it will be interpreted as a path
72
- in the Emscripten file system (Pyodide's file system). E.g.,
73
- ``emfs:../relative/path/wheel.whl`` or ``emfs:/absolute/path/wheel.whl``.
71
+ - If a wheel URI starts with ``emfs:``, it will be interpreted as a path \
72
+ in the Emscripten file system (Pyodide's file system). E.g., \
73
+ ``emfs:../relative/path/wheel.whl`` or ``emfs:/absolute/path/wheel.whl``. \
74
74
In this case, only .whl files are supported.
75
75
76
- - If a wheel URI requirement starts with ``http:`` or ``https:`` it will
76
+ - If a wheel URI requirement starts with ``http:`` or ``https:`` it will \
77
77
be interpreted as a URL.
78
78
79
- - In node, you can access the native file system using a URI that starts
79
+ - In node, you can access the native file system using a URI that starts \
80
80
with ``file:``. In the browser this will not work.
81
81
82
- keep_going :
82
+ keep_going:
83
83
84
84
This parameter decides the behavior of the micropip when it encounters a
85
85
Python package without a pure Python wheel while doing dependency
86
86
resolution:
87
87
88
- - If ``False``, an error will be raised on first package with a missing
88
+ - If ``False``, an error will be raised on first package with a missing \
89
89
wheel.
90
90
91
- - If ``True``, the micropip will keep going after the first error, and
91
+ - If ``True``, the micropip will keep going after the first error, and \
92
92
report a list of errors at the end.
93
93
94
- deps :
94
+ deps:
95
95
96
96
If ``True``, install dependencies specified in METADATA file for each
97
97
package. Otherwise do not install dependencies.
98
98
99
- credentials :
99
+ credentials:
100
100
101
101
This parameter specifies the value of ``credentials`` when calling the
102
102
`fetch() <https://developer.mozilla.org/en-US/docs/Web/API/fetch>`__
103
103
function which is used to download the package.
104
104
105
105
When not specified, ``fetch()`` is called without ``credentials``.
106
106
107
- pre :
107
+ pre:
108
108
109
109
If ``True``, include pre-release and development versions. By default,
110
110
micropip only finds stable versions.
111
111
112
- index_urls :
112
+ index_urls:
113
113
114
114
A list of URLs or a single URL to use as the package index when looking
115
115
up packages. If None, *https://pypi.org/pypi/{package_name}/json* is used.
116
116
117
- - The index URL should support the
117
+ - The index URL should support the \
118
118
`JSON API <https://warehouse.pypa.io/api-reference/json/>`__ .
119
119
120
- - The index URL may contain the placeholder {package_name} which will be
121
- replaced with the package name when looking up a package. If it does not
120
+ - The index URL may contain the placeholder {package_name} which will be \
121
+ replaced with the package name when looking up a package. If it does not \
122
122
contain the placeholder, the package name will be appended to the URL.
123
123
124
- - If a list of URLs is provided, micropip will try each URL in order until
124
+ - If a list of URLs is provided, micropip will try each URL in order until \
125
125
it finds a package. If no package is found, an error will be raised.
126
126
127
- constraints :
127
+ constraints:
128
128
129
129
A list of requirements with versions/URLs which will be used only if
130
130
needed by any ``requirements``.
131
131
132
132
Unlike ``requirements``, the package name _must_ be provided in the
133
133
PEP-508 format e.g. ``pkgname@https://...``.
134
134
135
- verbose :
135
+ verbose:
136
136
Print more information about the process. By default, micropip does not
137
137
change logger level. Setting ``verbose=True`` will print similar
138
138
information as pip.
0 commit comments