Skip to content

Commit 1eadb78

Browse files
authored
Merge pull request #9 from espressif/docs/add_rich_note
docs: Add note about using rich package
2 parents fe4017f + ad49bc7 commit 1eadb78

File tree

1 file changed

+21
-0
lines changed

1 file changed

+21
-0
lines changed

README.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -305,6 +305,27 @@ Signing is optional but strongly recommended. The action will produce a warning
305305
| `executable-extension` | File extension of built executables (e.g., `.exe` for Windows) |
306306
| `build-success` | Whether the build was successful (`true`/`false`) |
307307

308+
## Known Limitations
309+
310+
### Using `rich` Package
311+
312+
When using this action to build a binary that depends on `rich` it is recommended to add the following to the inputs:
313+
314+
```yaml
315+
with:
316+
additional-args: "--collect-submodules=rich._unicode_data"
317+
```
318+
319+
This is required for `rich>=14.3.0`, which introduced a new way of loading Unicode data.
320+
321+
`rich` uses dynamic imports. As a result, `PyInstaller` cannot always identify these imports as required, and it might not include them in the built binary.
322+
323+
Without the additional arguments to `PyInstaller`, executing the built binary might result in an error similar to the following:
324+
325+
```txt
326+
ModuleNotFoundError: No module named 'rich._unicode_data.unicode17-0-0'
327+
```
328+
308329
## Notes
309330

310331
- For 32-bit ARM architecture (linux-armv7), the action uses Docker containers to provide the necessary build environment

0 commit comments

Comments
 (0)