Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#78531 - [blender] is not including their static python
Attached to Project:
Community Packages
Opened by v (draic) - Tuesday, 16 May 2023, 10:40 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 16 May 2023, 21:23 GMT
Opened by v (draic) - Tuesday, 16 May 2023, 10:40 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 16 May 2023, 21:23 GMT
|
DetailsDescription: Blender is distributed with a static python version per release. This is done because Blender does some changes to Python in this special version to be able to address parts of Blender and it's objects via Python better. It also ensures interoperability for all Blender addons on all platforms. Several addons might not work with other Python versions and certain features are only possible with the modified Python that Blender distributes.
Only on Arch the repository package will use systems python which leads to several addons with broken features or refusing to start at all. I need to rely on using the binary download that Blender.org offers and the version from the repository is not usable. |
This task depends upon
Ugh, that's terrible. Arch tries to de-vendor wherever possible for obvious reasons. Did this problem only become worse when Arch upgraded to python-3.11? Ideally, upstream should get their stuff working with the latest python.