From 092b73aa483ea8c821d445126a3da8eee2aea7fa Mon Sep 17 00:00:00 2001 From: mejrs <59372212+mejrs@users.noreply.github.com> Date: Tue, 11 Jul 2023 13:56:34 +0200 Subject: [PATCH] Two is not three --- guide/src/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/src/faq.md b/guide/src/faq.md index a475b2fe..8308acc6 100644 --- a/guide/src/faq.md +++ b/guide/src/faq.md @@ -187,7 +187,7 @@ This happens on Windows when linking to the python DLL fails or the wrong one is - `python3X.dll` for Python 3.X, e.g. `python310.dll` for Python 3.10 - `python3.dll` when using PyO3's `abi3` feature -The DLL needs to be locatable using the [Windows DLL search order](https://learn.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-search-order#standard-search-order-for-unpackaged-apps). The two easiest ways to achieve this are: +The DLL needs to be locatable using the [Windows DLL search order](https://learn.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-search-order#standard-search-order-for-unpackaged-apps). Some ways to achieve this are: - Put the Python DLL in the same folder as your build artifacts - Add the directory containing the Python DLL to your `PATH` environment variable, for example `C:\Users\\AppData\Local\Programs\Python\Python310` - If this happens when you are *distributing* your program, consider using [PyOxidizer](https://github.com/indygreg/PyOxidizer) to package it with your binary.