The point IMO of parametric cad in an existing language is to use the ecosystem. Lots of choices in this project make that really hard.
The point IMO of parametric cad in an existing language is to use the ecosystem. Lots of choices in this project make that really hard.
On a more general note, I've mostly been using CadQuery to model pieces for 3d printing and the experience has been quite fun. Errors are not always easy to figure out and there's a learning curve to consider, but being able to "simply" describe my model in code instead of relying lots of [point|drag|click] is totally worth it. It was also a nice way to refresh my geometry knowledge.
[0] https://github.com/bernhard-42/jupyter-cadquery [1] https://hub.docker.com/r/bwalter42/jupyter_cadquery
https://github.com/CadQuery/cadquery/issues/153#issuecomment...
As an example of an approach that doesn't break Pypi, nltk distributes through Pypi but has an download() method for installation.
https://pypi.org/project/nltk/ https://www.nltk.org/data.html
The fact they're hostile towards pip (and ergo pipenv and poetry) just make it less than appealing software to want to use.
Understatement, if there ever was one.
Installing conda will maim your system irrevocably.