SolidPython VS OCP

https://github.com/SolidCode/SolidPython --- apparently there's a fork as a v2 which is to be preferred

Then use SolidPython to generate the scad files. ;)

I wonder how many OpenSCAD wrappers now exist? I know of scad-clj [0], openpyscad [1], and solidpython [2].

I particularly like scad-clj, because of `lein auto generate`. It watches source files, and regenerates the OpenSCAD files automatically, which OpenSCAD then also picks up. Although I'm not well versed in Clojure, and find debugging Clojure tricky, the workflow is just so good.

[0] https://github.com/farrellm/scad-clj

[1] https://github.com/taxpon/openpyscad

[2] https://github.com/SolidCode/SolidPython

Check out SolidPython, a front-end to OpenSCAD in Python that generates OpenSCAD code. It's actively developed (latest commit was 16 days ago) and has some excellent features, including first-class negative spaces - once you declare something to be a hole, the library makes sure that, no matter what, you will get a hole in the final model.

The mesh is already generated. I'm using a library (https://github.com/SolidCode/SolidPython) that generates OpenSCAD code which can be exported to pretty much any 3D format you want.

If you share an Excel (or, better yet, CSV) file, I can put up some Python code that outputs the OpenSCAD you want. I wrote SolidPython for exactly situations like this-- when you want to interface with other kinds of programs than just modeling.

In addition to first-class negative space (a hole like OP asked for), the SolidPython OpenSCAD binding also includes +, -, and * operators for union, difference, and intersection. (Disclosure; I’m the author)

Also, if it’s screw threads you’re after, there may just be some faster (== non-minkowski) ways to do that. OpenSCAD calculates polyhedrons much faster than big unions of parts. Buut, OpenSCAD also kinda sucks for doing vector math. I wrote SolidPython to get around some of the constrictions of OpenSCAD, and the screw_thread utility method should render decently detailed threads (120 segments per revolution, say) in a few seconds.

Even bigger problem is that it's riddled with hardcoded paths, redundant copies of files, disregarding recommended usage notes of its 3rd party libraries.. basically it contains every DevOps related anti-pattern you can think of.

There seems to be just one maintainer dealing with build related things and he is of a very different opinion what is anti-pattern or just don't want absolutely anybody to touch his code into which he poured his hours.

https://github.com/CadQuery/OCP/pull/61