1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
|
.. _extensions-python_wheels:
*************
Python Wheels
*************
.. TODO:
- Guidelines for wheel selecting the version to use.
- Finalize a policy for how conflicting versions of a wheel are handled.
`Python wheels <https://pythonwheels.com/>`__ (``*.whl``) are the standard way of distributing Python modules.
They are supported in Blender to make self-contained Python :ref:`Extensions <extensions-index>`.
Guidelines
==========
- By convention, always locate the files under ``./wheels/``.
Requirements
============
- Wheels must be bundled unmodified from `Python's package index <https://pypi.org>`__.
- Wheels must include their dependencies.
- Wheels filenames must match Python's binary distribution specification:
`see docs <https://packaging.python.org/en/latest/specifications/binary-distribution-format/#file-name-convention>`__.
*Wheels downloaded from Python's package index will follow this convention.*
- Use forward slashes as path separators when listing them on the
:ref:`manifest <extensions-manifest>`.
How to Bundle Wheels
====================
Python wheels (``*.whl``) can be bundled using the following steps.
Downloading Wheels
Download the wheel to the directory ``./wheels/``.
For wheels that are platform independent this example downloads ``jsmin``:
.. code-block:: console
pip wheel jsmin -w ./wheels
For wheels that contain binary compiled files, wheels for all supported platforms should be included:
This example downloads ``pillow`` - the popular image manipulation module.
.. code-block:: console
pip download pillow --dest ./wheels --only-binary=:all: --python-version=3.11 --platform=macosx_11_0_arm64
pip download pillow --dest ./wheels --only-binary=:all: --python-version=3.11 --platform=manylinux_2_28_x86_64
pip download pillow --dest ./wheels --only-binary=:all: --python-version=3.11 --platform=win_amd64
The available platform identifiers are listed on
`pillow's download page <https://pypi.org/project/pillow/#files>`__.
Update the Manifest
In ``blender_manifest.toml`` include the wheels as a list of paths, e.g.
.. code-block:: toml
wheels = [
"./wheels/pillow-10.3.0-cp311-cp311-macosx_11_0_arm64.whl",
"./wheels/pillow-10.3.0-cp311-cp311-manylinux_2_28_x86_64.whl",
"./wheels/pillow-10.3.0-cp311-cp311-win_amd64.whl",
]
Now installing the package will extract the wheel into the extensions own ``site-packages`` directory.
Running
Once the extension has been installed you can check the module is being loaded by importing it in the
Python console and printing it's location:
.. code-block:: python
import PIL
print(PIL.__file__)
Platform Builds
===============
Wheels can severely impact the size of an extension. To mitigate this, it is possible to build different
extension zip files for each unique required platform.
For this you need to use the ``--split-platforms`` option from the
:ref:`build <command-line-args-extension-build>` command.
.. code:: bash
blender --command extension build --split-platforms
Example
-------
Manifest file excerpt:
.. code-block:: toml
id = "my_addon_with_wheels"
version = "1.0.0"
platforms = ["windows-x64", "macos-x64"]
wheels = [
"./wheels/pillow-10.3.0-cp311-cp311-macosx_11_0_arm64.whl",
"./wheels/pillow-10.3.0-cp311-cp311-manylinux_2_28_x86_64.whl",
"./wheels/pillow-10.3.0-cp311-cp311-win_amd64.whl",
]
Generated files from ``--split-platforms``:
- my_addon_with_wheels-1.0.0-windows_x64.zip
- my_addon_with_wheels-1.0.0-macos_x64.zip
.. note::
Even though there is a Linux-only wheel present, no Linux zip file is generated.
This happens because the ``platforms`` field only has Mac and Windows.
|
