Skip to content

Commit c10c742

Browse files
authored
docs: Remove out-dated information for pyenv (#4138)
1 parent d1a0c72 commit c10c742

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

guide/src/building-and-distribution.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -232,7 +232,7 @@ not work when compiling for `abi3`. These are:
232232

233233
If you want to embed the Python interpreter inside a Rust program, there are two modes in which this can be done: dynamically and statically. We'll cover each of these modes in the following sections. Each of them affect how you must distribute your program. Instead of learning how to do this yourself, you might want to consider using a project like [PyOxidizer] to ship your application and all of its dependencies in a single file.
234234

235-
PyO3 automatically switches between the two linking modes depending on whether the Python distribution you have configured PyO3 to use ([see above](#configuring-the-python-version)) contains a shared library or a static library. The static library is most often seen in Python distributions compiled from source without the `--enable-shared` configuration option. For example, this is the default for `pyenv` on macOS.
235+
PyO3 automatically switches between the two linking modes depending on whether the Python distribution you have configured PyO3 to use ([see above](#configuring-the-python-version)) contains a shared library or a static library. The static library is most often seen in Python distributions compiled from source without the `--enable-shared` configuration option.
236236

237237
### Dynamically embedding the Python interpreter
238238

0 commit comments

Comments
 (0)