PythonOpenScad Yet Another Python Layer for OpenScad

PythonOpenScad (POSC)


PythonOpenScad is yet another OpenSCAD script/model generator with Python syntax.

The Python code below generates a 3D solid model of text saying ‘Hello world!’. This demostrates the OpenPyScad style API and in fact, apart from the import line and conversion to string in print, should execute as expected using OpenPyScad.

from pythonopenscad import Text


Text('Hello world!', size=15).linear_extrude(height=2)

.translate([-60, 0, 0]))

However, as an alternative, SolidPython style is also supported, like this.

from pythonopenscad import text, linear_extrude, translate


translate(v=[-60, 0, 0]) (

linear_extrude(height=2) (

text(text='Hello world!', size=15)




The generated OpenScad code in both cases above looks like the SolidPython style code with some interesting differences, note the braces ({}) which encapsulates the list of objects that the transforms apply to.

translate(v=[-60.0, 0.0, 0.0]) {

linear_extrude(height=2.0) {

text(text="Hello world!", size=15.0);



Note that the OpenScad script above is all using floating point numbers. This is because PythonOpenScad converts all parameters to their corresponding expected type.

If you paste this code into OpenScad you get this:


The best things come for free. You’re free to use your favourite Python IDE and get all the goodness of a full IDE experience. What doesn’t come for free but is very useful is listed below:

  • All POSC constructors are type checked. No generated scripts with junk inside them that’s hard to find where it happened and full debugger support comes for free.

  • Supports both OpenPyScad and SolidPython APIs for generating OpenScad code. Some differences exist between them on how the model looks like once it’s done.

  • Flexible code dump API to make it easy to add new functionality if desired.

  • POSC PyDoc strings have urls to all the implemented primitives.

  • Best of all, it does nothing else. Consider it a communication layer to OpenScad. Other functionality should be built as a different library.

POSC Compatability with the OpenPyScad and SolidPython APIs

Each POSC object contains member functions for all the OpenScad transformations. (BTW, these functions are simply wrapper functions over the transformation class constructors) This API style is more traditional of solid modelling APIs. However, the POSC implementation gives no preference between either and objects created with one API can be mixed and matched with objects created using the other API. All the OpenPyScad equivalent classes have capitalized names while the SolidPython classes have lower case names (the classes are different but they can be compared for equality). i.e.

>>> from pythonopenscad import Text, text

>>> Text() == text()


>>> Text('a') == text()


OpenPyScad’s modifier interface is not implemented but a different PythonOpenScad specific API accomplishes the same function. Modifiers are flags. In PythonOpenScad There are 4 flags, DISABLE, SHOW_ONLY, DEBUG and TRANSPARENT. They can be added and removed with the add_modifier, remove_modifier and has_modifiers functions.

Why Yet Another OpenScad Script Generator?

I mainly wanted a more functionality that was not being offered and it didn't seem OpenPyScad (my preferred style) was pulling changes very quickly (as luck would have it my small pull request was published about the same time I got PythonOpenScad working to a sufficiently stable state. I really want type checking/conversion and a bit more pydoc.

Apart from that, it seems that using Python to produce 3D solid models using OpenScad Is a prestigious line of work with a long and glorious tradition.

Here are some: active (kind of active) (gone) (2016) (2012) (2015) (2015) (2014)

It also seems like lots of dead projects but a popular theme nonetheless.

Given there are 2 active projects the big difference seems to be the API. SolidPython seems to mimic OpenScad like syntax (e,g, translate(v)cube()) while OpenPyScad employs a more common syntax (e.g. cube().translate()).

SolidPython appears to be much more active than OpenPyScad and contains a number of interesting enhancements with the inclusion of "holes". This can be positive or negative, I think negative. Personally I’d prefer another totally separate API layer that has much richer support and distances itself from the OpenScad api entirely.

So why did I write PythonOpenScad? I really don’t like the OpenScad syntax and I wanted a bit more error checking and flexibility with the supported data types. OpenPyScad could be a whole lot better and it seems like it needs a bit of a rewrite. It still supports Python 2 (and 3) but I wanted to move on.

PythonOpenScad is yet another OpenScad script generator (and only this). I will only entertain features that are specific to supporting OpenScad compatibility in PythonOpenScad . PythonOpenScad supports both the SolidPython and OpenPyScad solid modelling API. (i.e. all the OpenScad transforms, 3D and 2D shapes etc are supported.

  • Parameters are checked or converted and will raise exceptions if parameters are incompatible.

  • OpenScad defaults are applied so getting attribute values will result in actual values.

  • Documentation links to OpenScad reference docs can be found from help(object).

  • $fn/$fa/$fs is supported everywhere it actually does something even though the docs don’t say that they do.

  • repr(object) works and produces python code. similarly str(object) produces OpenScadCode.

PythonOpenScad code is very specifically only a layer to generate OpenScad scripts. I want to allow for one day where I will write bindings directly to a native OpenScad Python module that will allow more interesting interactions with the model. That’s for another day.

I have/am building another solid modelling tool, ParamertricSolids which allows building libraries of geometric solid models that will hopefully be a much easier way to build complex models. This is a layer on top of other CSG modules that hopefully will have a very independent relationship with OpenScad.