@ChengduLittleA Just to be sure, did you check to make sure that the pip
you are using is from a compatible version of Python (e.g. 3.11)? I did not run into any issue installing bpy==4.2.0
…
Hi @ChengduLittleA, just checking back in. Were able to repro my issue with the simplified script above?
Here is a more cut-down script:
import sys
import bpy
if len(sys.argv) != 2:
print(f"Usage: {sys.argv[0]} <file_path>")
sys.exit(1)
file_path = sys.argv[1]
#…
Hi @ChengduLittleA , it seems that the issue actually results from having loaded any gltf into the scene. Here is a script that illustrates the issue:
#!/usr/bin/env python
#…
@ideasman42 Just a note on the performance discrepancy mentioned for f-strings: It really depends on how they are used. Taking the test script from your SO question (https://stackoverflow.com/quest…
@olokobayusuf That's interesting, since I was able to install it into a Python 3.11 venv by just changing the name of the wheel file.
@LazyDodo Further investigation:
I opened an issue on the pdm
github page and the author suggested that the issue is actually on the Blender/packaging side due to an incorrect tag: https://git…
Seems that maybe it has something to do with the way that Python was built (I use mise
(previously called rtx
) but for this example, I tried using pdm
to install its own version of…
@LazyDodo Hmm, so you think that the issue is that pip
doesn't support the tag cp311-cp311-macosx_11_2_arm64
when it should? I am using the latest version of pip
, so it seems surprising that…
I was able to install the wheel directly by changing the name:
❯ eza -1 --group-directories-first
__pycache__
src
tests
bpy-4.1.0-cp311-cp311-macosx_11_0_arm64.whl -> ./bpy-4.1.0-cp31…
@LazyDodo Is it possible that the platform tag on the wheel is wrong somehow? From your comment, when I look at the output, I see that it finds this version:
Skipping link: none of the…
I also have this issue.
Apple M1 Pro macOS 13.6.4 (22G513)
I use pdm
to manage my Python projects and this is what I get when I create a new Python 3.11.8 project using the latest version…
@Mysteryem I guess it is more of a limitation, but it is not at all obvious that data is lost until you open the exported file since there are no errors or warnings. Also, my example doesn't show…