>Hi there! >This is my first message on the list, I'm Yorik, I'm architect, and I >contribute (quite modestly) to FreeCAD , another OCC-based project.
Hi York, Welcome to this list! >I seem to have a little problem running pythonOCC? I compiled it fine (on >debian testing), it runs fine, imports all submodules without errors, but >doing this, for example: > > > >>from OCC import gp >>p = gp.gp_Pnt(0,0,0) > >gives an error: > > > >>Traceback (most recent call last): >>File "<stdin>", line 1, in <module> >>File "/usr/lib/python2.5/site-packages/OCC/gp.py", line 4873, in __init__ >>this = _gp.new_gp_Pnt(*args) >>NotImplementedError: Wrong number of arguments for overloaded function >>'new_gp_Pnt'. >>Possible C/C++ prototypes are: >>gp_Pnt() >>gp_Pnt(gp_XYZ const &) >>gp_Pnt(Standard_Real const,Standard_Real const,Standard_Real const) Strange. You're the first to report this error. >Same thing happens with about any constructor where you use numbers. >So I conclude that python numbers are not recognized as Standard_Real const >Should I, before, turn my numbers into Standard_Real consts? How would I do >that? You don't have to worry about type conversion between C++ and Python. All that stuff is done by SWIG and does not require any additional manual tweak. So let me ask you a few questions: - what pythonOCC version did you compile? - what version of SWIG/gcc do you use? >Sorry if I ask for a very obvious thing, this is all very new to me... This bug is also very new to me! > >Cheers >Yorik Cheers, Thomas _______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
