I ran into a small problem here when trying to export a building model to IFC format with the ifcopenshell python package.
It seems like when FreeCAD attempts to parse the version string of ifcopenshell, it fails because the version of `ifcopenshell` contains non number characters inside.
I have documented the issue here on GH: https://github.com/FreeCAD/FreeCAD/issues/7957
I'm pretty new to the FreeCAD codebase in general. No too sure what to look for at this point. Any tips on this would be appreciated.
fail to parse ifcopenshell version from non numbers
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
Re: fail to parse ifcopenshell version from non numbers
Hi @obanana ,
Although I am only a very bad coder, I can try to propose a solution.
Give me some time!
Regards
PS: Can you add some more information: version number, operating system, ifc-file?
Although I am only a very bad coder, I can try to propose a solution.
Give me some time!
Regards
PS: Can you add some more information: version number, operating system, ifc-file?
Re: fail to parse ifcopenshell version from non numbers
In the meantime I found your information on Github.
The code for parsing the ifcopenshell version changed from FreeCAD 0.20 to FreeCAD 0.21 and most likely solved your problem.
Please try and report back
The code for parsing the ifcopenshell version changed from FreeCAD 0.20 to FreeCAD 0.21 and most likely solved your problem.
Please try and report back
Re: fail to parse ifcopenshell version from non numbers
Ah~ I see. thanks for checking in the repo. I think for my setup (Debian 11), I can just point my FreeCAD's remote to the FreeCAD, because whatever on Debian's repo is outdated. I think that usually solve the problem.
I think I can close this thread for now.
I think I can close this thread for now.
Re: fail to parse ifcopenshell version from non numbers
We could backport the fix to 0.20, though (it might take some time to make its way into debian, but it could help others). If you still have version 0.20 around, can you give the exact error message that you have?