> > > So, what are the ambitions for the following release? > > - #1 switch to OCE > - #2 the OCC.KBE module offers a high level, well structured pythonic > API > - #3 Henrik Rudstrøm has done a great job in providing excellent sphinx > based documentation, I'd love to see this project completed for the 0.6 > release > - #4 I'd like pythonocc to be well integrated with PyPi. Can you > imagine being able to install pythonocc like: "sudo pip install pythonocc"? > - #5 The > examples<http://code.google.com/p/pythonocc/source/browse/#svn%2Ftrunk%2Fsrc%2Fexamples%2FLevel1>are > very unpythonic and do not reflect the state of the project at all. The > examples will reflect the advancements made of the past 2 years. Refactor! > > Thomas and myself will focus on #1, #2 and #5. > Hopefully that answers your question "where do I pitch in?" > > Glad you asked; PyPi integration is an interesting project in itself, and > would be a huge boost for the pythonocc project. > Do I have a volunteer? >
I can try. Has the pythonOCC switch to OCE started? Or should I wait until that takes shape?
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
