Hi Thomas
Congrats on the new release! I have been out of the loop for a while
now, being extremely busy with new development, so I was wondering what
the status of the memory/garbage-collection issues are with the new release?
Regards,
Frank
On 25/01/2011 5:50 AM, Thomas Paviot wrote:
Dear all,
pythonOCC-0.5 is available for download at http://www.pythonocc.org.
The .tar.gz source archive was uploaded a couple of days ago, just the
time for me to package binary files for Windows before making this
announcement. Here is a shortlist of changes coming with this release
(376 svn commits from 0.4 to 0.5):
CHANGES FROM 0.4 to 0.5:
- Wrappers for C++ static methods have been implemented in a
SWIG compliant way. Static methods like: BRep_Tool::Surface() is now
callable with either BRep_Tool().Surface() or BRep_Tool_Surface()
- Improved project quality : 64 unittests currently pass
- Many improvements related to the graphic side (better
qtDisplay.py, abstraction of the CSF_GraphicShr env var)
- Multi selection of entities (vertices, edges, faces, shapes)
- Many fixes and improvements to the 'addons' or Level2 API (meshing,
PAF, new experimental DYN package, topology etc.)
- New samples (Traits based parametric modeling, display customization
etc.)
- License move from the GNU General Public License v3 (GPLv3) to the
GNU Lesser General Public License v3 (LGPLv3)
This release was successfully built/unittested under
MacOSX-py26/Ubuntu10.04-py26/WinXP-py25/Win7-py26. The Windows
packages for py25/py26 are built with Inno Setup : files are installed
to /site-packages and examples to /Program
Files/pythonOCC/0.5/examples. Shortcuts to these examples are inserted
to the Windows 'Start->Programs' menu. Windows users should report any
issue with these packages.
IMPORTANT NOTE:
- mixed CamelCase and lower_case methods naming, from the Level2 API,
were merge to a consistent pythonic lower_case. A few methods should
be affected, for instance the ReadFile or GetShapes methods of the
STEPImport class (moved to read_file and get_shapes). From now, this
consistent convention will be used : lower_case naming for python
extension to the wrapper, CamelCase for the OCC methods (the way it
used to be).
- the wrapping of static methods as python functions lead to a
conflict between the class TopoDS_Face() and the method TopoDS_Face()
coming from the C++ TopoDS::Face(). As a result, to avoid this
conflict, the static methods TopoDS::Vertex(), TopoDS::Face(),
TopoDS::Shell() etc. were renamed to vertex(), face() and shell() etc.
You can call them either with TopoDS().edge() or TopoDS_edge() (you
don't have to instanciate any TopoDS() object anymore to access these
methods). However, these changes are abstracted by the Utils.Topology
set of classes/functions.
These are the only changes to the API.
Please report any broken link or issue related to this release.
Best Regards,
Thomas
_______________________________________________
Pythonocc-users mailing list
Pythonocc-users@gna.org
https://mail.gna.org/listinfo/pythonocc-users
_______________________________________________
Pythonocc-users mailing list
Pythonocc-users@gna.org
https://mail.gna.org/listinfo/pythonocc-users
