base on A python parametric CAD scripting framework based on OCCT  # CadQuery [](https://ci.appveyor.com/project/jmwright/cadquery-o18bh/branch/master) [](https://dev.azure.com/cadquery/conda-packages/_build/latest?definitionId=2&branchName=master) [](https://codecov.io/gh/CadQuery/cadquery) [](https://cadquery.readthedocs.io/en/latest/?badge=latest) [](https://doi.org/10.5281/zenodo.4498634) --- ### Quick Links [***Documentation***](https://cadquery.readthedocs.io/en/latest/) | [***Cheatsheet***](https://cadquery.readthedocs.io/en/latest/_static/cadquery_cheatsheet.html) | [***Discord***](https://discord.com/invite/Bj9AQPsCfx) | [***Google Group***](https://groups.google.com/g/cadquery) | [***GUI Editor***](https://github.com/CadQuery/CQ-editor) --- ## What is CadQuery CadQuery is an intuitive, easy-to-use Python module for building parametric 3D CAD models. Using CadQuery, you can write short, simple scripts that produce high quality CAD models. It is easy to make many different objects using a single script that can be customized. CadQuery is often compared to [OpenSCAD](http://www.openscad.org/). Like OpenSCAD, CadQuery is an open-source, script based, parametric model generator. However, CadQuery stands out in many ways and has several key advantages: 1. The scripts use a standard programming language, Python, and thus can benefit from the associated infrastructure. This includes many standard libraries and IDEs. 2. CadQuery's CAD kernel Open CASCADE Technology ([OCCT](https://en.wikipedia.org/wiki/Open_Cascade_Technology)) is much more powerful than the [CGAL](https://en.wikipedia.org/wiki/CGAL) used by OpenSCAD. Features supported natively by OCCT include NURBS, splines, surface sewing, STL repair, STEP import/export, and other complex operations, in addition to the standard CSG operations supported by CGAL 3. Ability to import/export [STEP](https://en.wikipedia.org/wiki/ISO_10303) and the ability to begin with a STEP model, created in a CAD package, and then add parametric features. This is possible in OpenSCAD using STL, but STL is a lossy format. 4. CadQuery scripts require less code to create most objects, because it is possible to locate features based on the position of other features, workplanes, vertices, etc. 5. CadQuery scripts can build STL, STEP, AMF and 3MF faster than OpenSCAD. CadQuery was built to be used as a Python library without any GUI. This makes it great for use cases such as integration into servers, or creating scientific and engineering scripts. Options for visualization are also available including CQ-Editor and JupyterLab. For those who are interested, the [OCP repository](https://github.com/CadQuery/OCP) contains the current OCCT wrapper used by CQ. ### Key features * Build 3D models with scripts that are as close as possible to how you would describe the object to a human. * Create parametric models that can be very easily customized by end users. * Output high quality (loss-less) CAD formats like STEP and DXF in addition to STL, VRML, AMF and 3MF. * Provide a non-proprietary, plain text model format that can be edited and executed with only a web browser. * Offer advanced modeling capabilities such as fillets, curvilinear extrudes, parametric curves and lofts. * Build nested assemblies out of individual parts and other assemblies. ### Why this fork The original version of CadQuery was built on the FreeCAD API. This was great because it allowed for fast development and easy cross-platform capability. However, we eventually started reaching the limits of the API for some advanced operations and selectors. This 2.0 version of CadQuery is based directly on a Python wrapper of the OCCT kernel. This gives us a great deal more control and flexibility, at the expense of some simplicity and having to handle the cross-platform aspects of deployment ourselves. We believe this is a worthwhile trade-off to allow CadQuery to continue to grow and expand in the future. ## Getting started To learn more about designing with CadQuery, visit the [documentation](https://cadquery.readthedocs.io/en/latest/intro.html), [examples](https://cadquery.readthedocs.io/en/latest/examples.html), and [cheatsheet](https://cadquery.readthedocs.io/en/latest/_static/cadquery_cheatsheet.html). To get started playing around with CadQuery and see its capabilities, take a look at the [CQ-editor GUI](https://github.com/CadQuery/CQ-editor). This easy-to-use IDE is a great way to get started desiging with CadQuery. The CQ-editor installer bundles both CQ-editor and CadQuery (recommended). See the [CQ-editor installation instructions](https://cadquery.readthedocs.io/en/latest/installation.html#adding-a-nicer-gui-via-cq-editor). The CadQuery library (with or without CQ-editor) and its dependencies may be installed using conda, or pip. Note that conda (or the CQ-editor installer) is the better supported option. See the documentation for detailed CadQuery [installation instructions](https://cadquery.readthedocs.io/en/latest/installation.html). There are also videos covering installation: * Linux [installation video](https://youtu.be/sjLTePOq8bQ) * Windows [installation video](https://youtu.be/3Tg_RJhqZRg) ### CadQuery Installation Via Conda To first install the Conda package manager see [Install the Conda Package Manager](https://cadquery.readthedocs.io/en/latest/installation.html#install-the-conda-package-manager), and [Miniforge](https://github.com/conda-forge/miniforge) for a minimal installer. ``mamba install`` is recommended over ``conda install`` for faster and less memory intensive cadquery installation. ``` # Set up a new environment conda create -n cadquery # Activate the new environment conda activate cadquery # Install the latest released version mamba install -c conda-forge cadquery # Or install the dev version to get the latest changes mamba install -c conda-forge -c cadquery cadquery=master ``` ### CadQuery Installation Via Pip CadQuery has a complex set of dependencies including OCP, which is our set of bindings to the OpenCASCADE CAD kernel. OCP is distributed as binary wheels for Linux, MacOS and Windows. However, there are some limitations. Only Python 3.9 through 3.12 are currently supported, and some older Linux distributions such as Ubuntu 18.04 are not supported. If the pip installation method does not work for your system, you can try the conda installation method. It is highly recommended that a virtual environment is used when installing CadQuery, although it is not strictly required. Installing CadQuery via pip requires a up-to-date version of pip, which can be obtained with the following command line (or a slight variation thereof). ``` python3 -m pip install --upgrade pip ``` Once a current version of pip is installed, CadQuery can be installed using the following command line. ``` pip install cadquery ``` It is also possible to install the very latest changes directly from CadQuery's GitHub repository, with the understanding that sometimes breaking changes can occur. To install from the git repository, run the following command line. ``` pip install git+https://github.com/CadQuery/cadquery.git ``` ### CQ-editor GUI CQ-editor is an IDE that allows users to edit CadQuery model scripts in a GUI environment. It includes features such as: * A graphical debugger that allows you to step through your scripts. * A CadQuery stack inspector. * Export to various formats, including STEP and STL, directly from the menu. More on CQ-editor: * [CQ-editor README](https://github.com/CadQuery/CQ-editor/blob/master/README.md) * [Installation](https://cadquery.readthedocs.io/en/latest/installation.html#adding-a-nicer-gui-via-cq-editor) <img src="https://raw.githubusercontent.com/CadQuery/CQ-editor/master/screenshots/screenshot3.png" alt="CQ editor screenshot" width="800"/> ### Jupyter CadQuery supports Jupyter out-of-the-box. Run your CadQuery code in the notebook and visualize the model by calling ```display(<CadQuery object>)```. * [JupyterLab installation](https://cadquery.readthedocs.io/en/latest/installation.html#jupyter). ## Getting help You can find the full CadQuery documentation at [cadquery.readthedocs.io](https://cadquery.readthedocs.io/). We also have a [Google Group](https://groups.google.com/forum/#!forum/cadquery) to make it easy to get help from other CadQuery users. We want you to feel welcome and encourage you to join the group and introduce yourself. We would also love to hear what you are doing with CadQuery. There is a [Discord server](https://discord.gg/Bj9AQPsCfx) as well. You can ask for help in the _general_ channel. ## Projects using CadQuery Here are just a few examples of how CadQuery is being used. ### FxBricks Lego Train System [FxBricks](https://fxbricks.com/) uses CadQuery in the product development pipeline for their Lego train system. FxBricks has also given back to the community by creating [documentation for their CAD pipeline](https://github.com/fx-bricks/fx-cad-notes). They have also assembled [cq-kit](https://github.com/michaelgale/cq-kit), a library containing utility classes and functions to extend the capabilities of CadQuery. Thanks to @michaelgale and @fx-bricks for this example.  ### Hexidor Board Game Development Hexidor is an expanded take on the Quoridor board game, and the development process has been chronicled [here](https://bruceisonfire.net/2020/04/23/my-adventure-with-flosscad-the-birth-of-hexidor/). CadQuery was used to generate the game board. Thanks to Bruce for this example. <img src="https://bruceisonfire.net/wp-content/uploads/2020/04/16-945x709.jpg" alt="Hexidor Board Game" width="400"/> ### Spindle assembly Thanks to @marcus7070 for this example from [here](https://github.com/marcus7070/spindle-assy-example). <img src="./doc/_static/assy.png" width="400"> ### 3D Printed Resin Mold Thanks to @eddieliberato for sharing [this example](https://jungletools.blogspot.com/2017/06/an-anti-kink-device-for-novel-high-tech.html) of an anti-kink resin mold for a cable. <img src="https://3.bp.blogspot.com/-2FiHOGUhtxo/WTRsViGdOXI/AAAAAAAAA-E/sb5ehwPVr-EncYC8RM2-v21M3AAmbjUjQCLcB/s1600/Screenshot%2Bfrom%2B2017-06-04%2B22-05-07.png" alt="3D printed resin mold" height="250"/> ## License CadQuery is licensed under the terms of the [Apache Public License, version 2.0](http://www.apache.org/licenses/LICENSE-2.0). ## Contributing Contributions from the community are welcome and appreciated. You do not need to be a software developer to have a big impact on this project. Contributions can take many forms including, but not limited to, the following: * Writing and improving documentation * Triaging bugs * Submitting bugs and feature requests * Creating tutorial videos and blog posts * Helping other users get started and solve problems * Telling others about this project * Helping with translations and internationalization * Helping with accessibility * Contributing bug fixes and new features It is asked that all contributions to this project be made in a respectful and considerate way. Please use the [Python Community Code of Conduct's](https://www.python.org/psf/codeofconduct/) guidelines as a reference. ### Contributing code If you are going to contribute code, make sure to follow this steps: - Consider opening an issue first to discuss what you have in mind - Try to keep it as short and simple as possible (if you want to change several things, start with just one!) - Fork the CadQuery repository, clone your fork and create a new branch to start working on your changes - Create a conda development environment with something like: - `mamba env create -n cq-dev -f environment.yml` - Activate the new conda environment: - `conda activate cq-dev` - If desired, install the master branch of cq-editor (Note; a release version may not be compatible with the master branch of cadquery): - `mamba install -c cadquery -c conda-forge cq-editor=master` Installing cq-editor adds another instance of cadquery which overrides the clone just added. Fix this by reinstalling cadquery using pip: - `pip install -e .` - Before making any changes verify that the current tests pass. Run `pytest` from the root of your cadquery clone, there should be no failures and the output will look similar to this: - ======= 215 passed, 57 warnings in 13.95s ======= - Start with the tests! How should CadQuery behave after your changes? Make sure to add some tests to the test suite to ensure proper behavior - Make sure your tests have assertions checking all the expected results - Add a nice docstring to the test indicating what the test is doing; if there is too much to explain, consider splitting the test in two! - Go ahead and implement the changes - Add a nice docstring to the functions/methods/classes you implement describing what they do, what the expected parameters are and what it returns (if anything) - Update the documentation if there is any change to the public API - Consider adding an example to the documentation showing your cool new feature! - Make sure nothing is broken (run the complete test suite with `pytest`) - Run `black` from [our fork](https://github.com/CadQuery/black) to autoformat your code and make sure your code style complies with CadQuery's - Push the changes to your fork and open a pull-request upstream - Keep an eye on the automated feedback you will receive from the CI pipelines; if there is a test failing or some code is not properly formatted, you will be notified without human intervention - Be prepared for constructive feedback and criticism! - Be patient and respectful, remember that those reviewing your code are also working hard (sometimes reviewing changes is harder than implementing them!) ### How to Report a Bug When filing a bug report [issue](https://github.com/CadQuery/cadquery/issues), please be sure to answer these questions: 1. What version of the software are you running? 2. What operating system are you running the software on? 3. What are the steps to reproduce the bug? ### How to Suggest a Feature or Enhancement If you find yourself wishing for a feature that does not exist, you are probably not alone. There are bound to be others out there with similar needs. Open an [issue](https://github.com/CadQuery/cadquery/issues) which describes the feature you would like to see, why you need it, and how it should work. ", Assign "at most 3 tags" to the expected json: {"id":"11757","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"