You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed this when trying to save a blender file with the current versioning system, the following error pops up:
ValueError: bpy_struct: item.attr = val: sequences of dimension 0 should contain 3 items, not 10
The reason this happens is I think that a tuple is expected, however that tuple is converted to string and is then being sent to blender.
The old code before the changes was:
defget_addon_version():
from .importbl_inforeturnbl_info["version"]
defwrite_addon_version(context):
version=get_addon_version()
logger.debug("Writting addon version: "+str(version))
# NOTE: Version is written to every scene because there's no global# place we can put this valueforsceneinbpy.data.scenes:
scene.sketcher.version=version
the changes splitted the get_addon_version function into another file and made get_addon_version return a string:
defget_bl_info():
from .. importbl_inforeturnbl_infodefget_addon_version() ->str:
"""Return addon version from manifest file"""ifversion< (4, 20):
returnstr(get_bl_info()["version"])
manifest=pathlib.Path(__file__).parent.parent/"blender_manifest.toml"try:
importtomlreturntoml.load(manifest)["blender"]
exceptException:
return""
The bigger issue is that it seems like any file that has been saved from new since this change with blender version < 4.20 will have no version info at all....
So version updating does not seem to happen anymore because it passes here without a set version prop:
Contact Details
No response
Description
I noticed this when trying to save a blender file with the current versioning system, the following error pops up:
ValueError: bpy_struct: item.attr = val: sequences of dimension 0 should contain 3 items, not 10
The reason this happens is I think that a tuple is expected, however that tuple is converted to string and is then being sent to blender.
The old code before the changes was:
the changes splitted the get_addon_version function into another file and made get_addon_version return a string:
The bigger issue is that it seems like any file that has been saved from new since this change with blender version < 4.20 will have no version info at all....
So version updating does not seem to happen anymore because it passes here without a set version prop:
Addon Version
0.27.3
Blender Version
4.1
What platform are you running on?
Linux
The text was updated successfully, but these errors were encountered: