Dear all, Since the latest pythonOCC release (0.5), a major event occured: OpenCASCADE 6.5.0 was released. pythonOCC provides a python wrapper to this C++ library, this event then significantly impacts our work. When OCC 6.5.0 was released, three question arised: 1. does pythonocc support 6.5.0 release? 2. is the port planned? 3. if yes, when?
Here are my three answers: 1. No. Currently, pythonocc only supports OpenCASCADE 6.3.0. The SWIG files, allowing building the wrapper, need to be updated to the latest OCC release. This is not as 'automagic' as I expected ;-) 2. not exactly. 3. in the coming weeks. Let me explain the points 2 and 3. OpenCASCADE 6.3.0 was released in 2008. There have been severel 'intermediate' releases in the meantime, but only intended to OpenCascade customers. Open Source users were just frustrated to see improvements only available for customers (whereas a few of these improvements were contributed by the open source community itself). The community often requested for a real open source project management from the OCC company. But nothing came. Open source community was just despised. At last, one month ago, the version 6.5.0 was released and made available to the whole community, not only to customers. As soon as 6.5.0 was released, a few of us decided to create another project named 'OCE' (Opencascade Community Edition), announced on the OCC forum (see http://www.opencascade.org/org/forum/thread_20111/). We just made by ourselves what we'd been expecting from the OCC company for years: a public repository to host patches/improvements from the community, an issue tracker etc. That is to say a set of tools that ensure that this fantastic library will never die. Furthermore, a set of tools to make it live. The project is quite active, many patches were already commited, and we're about to release the 0.1 version, which brings a lot of small improvements/bugfixes over OCC 6.5.0. So the exact answer to question 2 is: no, the next pythonocc release will not be based on OCC 6.5.0 but on OCE 0.1 (the two libraries are currently binary compliant, no divergence is planned yet). Answer 3: as soon as OCE 0.1 is released, I will commit changes to the pythonocc svn repository (a big part of the port job has already be done on my machine) to support OCE. You're welcome to join the OCE project: as a user or a developer. We need the opinion/ideas/compilation feedbacks from all of you. Technical discussions are hosted on the oce-dev google group: http://groups.google.com/group/oce-dev, whereas the source code is hosted at github: https://github.com/tpaviot/oce/. We do believe, at OCE, that a dynamic OCC/OCE ecosystem is necessary for the OCC/OCE related project to be alive: FreeCad, CadExchanger, pythonocc, HeeksCAD etc. It is all our interest that the OCE project is a success. Thomas CC to oce-dev, sorry for cross-posting. Do not 'reply all' if you registered both pythonocc-users and oce-dev.
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
