-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
hook: win32ctypes.core: always collect the ctypes backend
Always collect the `ctypes` backend (`win32ctypes.core.ctypes` modules), even if we are also collecting the `cffi` backend due to `cffi` being available in the build environment. This prevents issues when import of `cffi` is blocked at run-time (similarly to how we do it to avoid issues with -OO optimization level) or when `cffi` is excluded from collection by user (for example, by using `--exclude-module cffi`).
- Loading branch information
Showing
2 changed files
with
13 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
The ``pywin32-ctypes`` hook now always collects the ``win32ctypes.core.ctypes`` | ||
modules, so that the ``ctypes`` backend is always available (i.e., even | ||
if we also collect the ``cffi`` backend due to availability of ``cffi`` | ||
in the build environment). This fixes issues when ``cffi`` ends up | ||
unavailable at run-time in spite of being available in the build environment | ||
at build time (for example, due to explicit exclusion via :option:`--exclude-module` | ||
option). |