@@ -265,10 +265,10 @@ Pyodide uses the ``ZipImporter`` approach in every runtime. Python uses the
265265NODEFS approach when run with node and the ``ZipImporter `` approach for the web
266266example. We will continue with this approach.
267267
268- The `ZipImporter ` provides a clean resolution for a bootstrapping problem: The
268+ The `` ZipImporter ` ` provides a clean resolution for a bootstrapping problem: The
269269Python runtime is capable of unpacking a wide variety of archive formats, but
270270the Python runtime is not ready to use until the standard library is already
271- available. Since `zipimport.py ` is a frozen module, it avoids these problems.
271+ available. Since `` zipimport.py ` ` is a frozen module, it avoids these problems.
272272All of the other approaches solve the bootstrapping problem by setting up the
273273standard library using JavaScript.
274274
@@ -284,11 +284,11 @@ uses two different approaches for packages:
284284 The work of downloading and installing all the packages is redone every time
285285 the runtime starts.
286286
287- * The Pyodide `python ` cli entrypoint mounts all of the host file system as
287+ * The Pyodide `` python ` ` cli entrypoint mounts all of the host file system as
288288 NODEFS directories before it bootstraps Python. This allows the normal virtual
289289 environment mechanism to work. Pyodide virtual environments contain a patched
290- copy of pip and a custom `pip.conf ` so that pip will install Pyodide wheels.
291- On startup the Pyodide `python ` cli will preload all Emscripten dynamic
290+ copy of pip and a custom `` pip.conf ` ` so that pip will install Pyodide wheels.
291+ On startup the Pyodide `` python ` ` cli will preload all Emscripten dynamic
292292 libraries that are in the sitee-packages directory.
293293
294294
0 commit comments