molejo 0.1.0__tar.gz

molejo-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

molejo-0.1.0/MANIFEST.in

@@ -0,0 +1,5 @@
+# The test suite is a repository asset, not a source-distribution one: it
+# reads the shared parity fixtures at `fixtures/`, one level above this
+# package directory and outside anything an sdist may contain. Shipping it
+# would ship a suite that cannot run. Clone the repository to run the tests.
+prune tests

molejo-0.1.0/NOTICE

@@ -0,0 +1,2 @@
+molejo - analytic flexible parts for mechanical CAD
+Copyright (C) 2026 Luis Henrique Cassis Fagundes

molejo-0.1.0/PKG-INFO

@@ -0,0 +1,169 @@
+Metadata-Version: 2.4
+Name: molejo
+Version: 0.1.0
+Summary: Analytic flexible parts for mechanical CAD: parametric swept shapes evaluated identically in Python and the browser
+Author-email: Luis Henrique Cassis Fagundes <lhfagundes@gmail.com>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/LibreSolid/molejo
+Project-URL: Documentation, https://molejo.readthedocs.io
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Manufacturing
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Multimedia :: Graphics :: 3D Modeling
+Classifier: Topic :: Scientific/Engineering
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: numpy
+Provides-Extra: brep
+Requires-Dist: cadquery-ocp; extra == "brep"
+Dynamic: license-file
+
+# molejo
+
+*The give in your machine.*
+
+**molejo** (Brazilian Portuguese: the springy give of a thing) is an
+analytic representation for the flexible parts of a machine — valve
+springs, timing belts, cable looms, filament — parts whose *shape* is a
+function of machine state, not just their placement.
+
+A molejo shape is a serializable **spec**: a planar profile swept along a
+parametric path, whose numeric slots may reference named scalar
+parameters. The spec is the model. Meshes are evaluations of it:
+
+- the **Python evaluator** turns a spec plus parameter values into an
+  exact triangle mesh (and STL) for build pipelines, geometric tests,
+  and collision checks;
+- the **JavaScript evaluator** turns the same spec plus the same values
+  into vertex buffers for three.js, cheap enough to re-evaluate every
+  animation frame;
+- an optional **B-rep evaluator** (OCCT, via the `brep` extra of the
+  Python package) turns the same spec plus the same values into an
+  exact solid, for testing architectures that assert on exact shapes.
+
+Both evaluators emit the same vertex count in the same order by
+construction — tessellation is fixed and declared in the spec, never
+curvature-adaptive — and are pinned to each other by shared parity
+fixtures.
+
+Full documentation: <https://molejo.readthedocs.io>
+
+## What it looks like
+
+Authoring is Python-first; the JSON spec is the representation it
+serializes to:
+
+```python
+from molejo import Shape, Circle, Helix, P
+
+spring = Shape(
+    profile=Circle(radius=2.0),
+    path=[Helix(radius=14.0, turns=6.5, height=P.height)],
+    path_samples=240, profile_samples=16,
+)
+
+mesh = spring.evaluate(height=46.8)   # numpy vertices and faces
+spring.to_json()                      # the spec — what a browser gets
+```
+
+`P.height` is a plain reference, not an expression: derived values
+(`free_length - lift`) are computed in ordinary Python and bound at
+evaluation. The browser side consumes the serialized spec only:
+
+```js
+import { evaluate } from 'molejo';
+evaluate(spec, { height: 50.0 - lift(t) }, buffers); // per frame, in place
+```
+
+## Why
+
+CAD kernels represent rigid geometry; animation systems interpolate
+placement. A compressing spring, a circulating belt, or a cable loom
+following a print head falls between the two: its geometry at any
+instant is exact, closed-form math over a few scalars (a lift, a
+carriage position), but no kernel evaluates that math in both a build
+pipeline and a browser at frame rate.
+
+Sampling the shape (morph targets, frame swapping) works for one
+parameter and dies combinatorially at two or three — a loom that follows
+X, Y and Z would need a sampled grid over all of them. molejo instead
+keeps the shape analytic and moves the *evaluation* to wherever it is
+needed.
+
+## Design properties
+
+- **Analytic master, evaluations on demand.** The spec defines exact
+  curves and surfaces; every mesh is a deterministic sampling of them
+  at the declared resolution, and the B-rep evaluator constructs the
+  same curves exactly in OCCT. Line- and arc-based sweeps (belts) are
+  analytic surfaces; helix and spline sweeps are tolerance-declared
+  B-spline surfaces, as in any kernel.
+- **Sweeps only, no booleans.** A closed profile swept along a path is
+  watertight by construction; there is no repair pass because no input
+  can be broken. Boolean interaction belongs to whatever mesh machinery
+  consumes the evaluation.
+- **Parameters are plain named numbers.** molejo does not know where
+  they come from — a slider, a kinematic expression, a test instant.
+  Expression languages belong to the consumer.
+- **Continuity and self-intersection are the author's obligation.** The
+  representation does not police an over-compressed spring; the
+  consumer's tests can.
+
+## Status
+
+Version 0.1.0, implementing spec version 1: profiles (circle, polygon)
+and path primitives (line, arc, helix, spline, wrap). Both packages
+parse and validate the document against shared fixtures; the Python
+package also authors it (`Shape`, `Circle`, …, `P`).
+
+Circle and polygon profiles swept along the whole v1 path vocabulary —
+`line`, `arc`, `helix`, `spline` and `wrap` — evaluate in both runtimes,
+singly or chained, capped or closed into a loop and watertight either
+way, from Python as numpy arrays and binary STL, from JavaScript as
+reusable three.js buffers, pinned to each other by shared parity
+fixtures. The spring in the sample above is one of those fixtures rather
+than a promise, and so are a toothed belt around three pulleys whose
+teeth circulate with a parameter and a filament loom whose head follows
+three. The one gap in the v1 vocabulary raises naming itself: closing a
+loop that is not a wrap.
+
+The B-rep evaluator installs with `pip install molejo[brep]` and
+evaluates the same documents to closed OCCT solids —
+`molejo.brep.evaluate(spec, values)` or `shape.brep(**values)` — with the
+same refusals, word for word, as the mesh evaluator. Every parity fixture
+is checked through it on volume and area. An install without the extra
+imports and meshes and exports STL exactly as before; asking it for a
+solid raises naming the extra.
+
+molejo 0.1 has done real work before being called a release: it is the
+flexible-part representation of [solid-node](https://github.com/LibreSolid/solid-node)
+machine models, where its springs and belts hold up in animated,
+geometrically tested engines and 3D printers (a V8 engine's valve
+springs, a Metamaquina 2's drive belts) rather than only in this
+repository's fixtures.
+
+A package version carries the spec version it implements. Both packages
+carry spec v1 at `0.1.0` and release together for a given spec version.
+One document, two implementations: neither runtime is ever published
+against a spec version the other has not caught up to.
+
+Publishing to PyPI (`python/`) and npm (`js/`) is the maintainer's
+explicit decision, never a side effect of building: `scripts/check-dist`,
+the release dry-run, packs each package, installs it into a throwaway
+environment outside this repository and evaluates a fixture there — and
+uploads nothing.
+
+## Origin
+
+molejo was born from [solid-node](https://github.com/LibreSolid/solid-node),
+a Python framework for mechanical CAD projects, which needed springs,
+belts and cable looms in animated, testable machine models. solid-node
+adapts molejo as one leaf-geometry technology among the several it
+supports; molejo itself is independent and consumable by any Python or
+three.js project.
+
+## License
+
+Apache License 2.0 — see `LICENSE`.

molejo-0.1.0/README.md

@@ -0,0 +1,147 @@
+# molejo
+
+*The give in your machine.*
+
+**molejo** (Brazilian Portuguese: the springy give of a thing) is an
+analytic representation for the flexible parts of a machine — valve
+springs, timing belts, cable looms, filament — parts whose *shape* is a
+function of machine state, not just their placement.
+
+A molejo shape is a serializable **spec**: a planar profile swept along a
+parametric path, whose numeric slots may reference named scalar
+parameters. The spec is the model. Meshes are evaluations of it:
+
+- the **Python evaluator** turns a spec plus parameter values into an
+  exact triangle mesh (and STL) for build pipelines, geometric tests,
+  and collision checks;
+- the **JavaScript evaluator** turns the same spec plus the same values
+  into vertex buffers for three.js, cheap enough to re-evaluate every
+  animation frame;
+- an optional **B-rep evaluator** (OCCT, via the `brep` extra of the
+  Python package) turns the same spec plus the same values into an
+  exact solid, for testing architectures that assert on exact shapes.
+
+Both evaluators emit the same vertex count in the same order by
+construction — tessellation is fixed and declared in the spec, never
+curvature-adaptive — and are pinned to each other by shared parity
+fixtures.
+
+Full documentation: <https://molejo.readthedocs.io>
+
+## What it looks like
+
+Authoring is Python-first; the JSON spec is the representation it
+serializes to:
+
+```python
+from molejo import Shape, Circle, Helix, P
+
+spring = Shape(
+    profile=Circle(radius=2.0),
+    path=[Helix(radius=14.0, turns=6.5, height=P.height)],
+    path_samples=240, profile_samples=16,
+)
+
+mesh = spring.evaluate(height=46.8)   # numpy vertices and faces
+spring.to_json()                      # the spec — what a browser gets
+```
+
+`P.height` is a plain reference, not an expression: derived values
+(`free_length - lift`) are computed in ordinary Python and bound at
+evaluation. The browser side consumes the serialized spec only:
+
+```js
+import { evaluate } from 'molejo';
+evaluate(spec, { height: 50.0 - lift(t) }, buffers); // per frame, in place
+```
+
+## Why
+
+CAD kernels represent rigid geometry; animation systems interpolate
+placement. A compressing spring, a circulating belt, or a cable loom
+following a print head falls between the two: its geometry at any
+instant is exact, closed-form math over a few scalars (a lift, a
+carriage position), but no kernel evaluates that math in both a build
+pipeline and a browser at frame rate.
+
+Sampling the shape (morph targets, frame swapping) works for one
+parameter and dies combinatorially at two or three — a loom that follows
+X, Y and Z would need a sampled grid over all of them. molejo instead
+keeps the shape analytic and moves the *evaluation* to wherever it is
+needed.
+
+## Design properties
+
+- **Analytic master, evaluations on demand.** The spec defines exact
+  curves and surfaces; every mesh is a deterministic sampling of them
+  at the declared resolution, and the B-rep evaluator constructs the
+  same curves exactly in OCCT. Line- and arc-based sweeps (belts) are
+  analytic surfaces; helix and spline sweeps are tolerance-declared
+  B-spline surfaces, as in any kernel.
+- **Sweeps only, no booleans.** A closed profile swept along a path is
+  watertight by construction; there is no repair pass because no input
+  can be broken. Boolean interaction belongs to whatever mesh machinery
+  consumes the evaluation.
+- **Parameters are plain named numbers.** molejo does not know where
+  they come from — a slider, a kinematic expression, a test instant.
+  Expression languages belong to the consumer.
+- **Continuity and self-intersection are the author's obligation.** The
+  representation does not police an over-compressed spring; the
+  consumer's tests can.
+
+## Status
+
+Version 0.1.0, implementing spec version 1: profiles (circle, polygon)
+and path primitives (line, arc, helix, spline, wrap). Both packages
+parse and validate the document against shared fixtures; the Python
+package also authors it (`Shape`, `Circle`, …, `P`).
+
+Circle and polygon profiles swept along the whole v1 path vocabulary —
+`line`, `arc`, `helix`, `spline` and `wrap` — evaluate in both runtimes,
+singly or chained, capped or closed into a loop and watertight either
+way, from Python as numpy arrays and binary STL, from JavaScript as
+reusable three.js buffers, pinned to each other by shared parity
+fixtures. The spring in the sample above is one of those fixtures rather
+than a promise, and so are a toothed belt around three pulleys whose
+teeth circulate with a parameter and a filament loom whose head follows
+three. The one gap in the v1 vocabulary raises naming itself: closing a
+loop that is not a wrap.
+
+The B-rep evaluator installs with `pip install molejo[brep]` and
+evaluates the same documents to closed OCCT solids —
+`molejo.brep.evaluate(spec, values)` or `shape.brep(**values)` — with the
+same refusals, word for word, as the mesh evaluator. Every parity fixture
+is checked through it on volume and area. An install without the extra
+imports and meshes and exports STL exactly as before; asking it for a
+solid raises naming the extra.
+
+molejo 0.1 has done real work before being called a release: it is the
+flexible-part representation of [solid-node](https://github.com/LibreSolid/solid-node)
+machine models, where its springs and belts hold up in animated,
+geometrically tested engines and 3D printers (a V8 engine's valve
+springs, a Metamaquina 2's drive belts) rather than only in this
+repository's fixtures.
+
+A package version carries the spec version it implements. Both packages
+carry spec v1 at `0.1.0` and release together for a given spec version.
+One document, two implementations: neither runtime is ever published
+against a spec version the other has not caught up to.
+
+Publishing to PyPI (`python/`) and npm (`js/`) is the maintainer's
+explicit decision, never a side effect of building: `scripts/check-dist`,
+the release dry-run, packs each package, installs it into a throwaway
+environment outside this repository and evaluates a fixture there — and
+uploads nothing.
+
+## Origin
+
+molejo was born from [solid-node](https://github.com/LibreSolid/solid-node),
+a Python framework for mechanical CAD projects, which needed springs,
+belts and cable looms in animated, testable machine models. solid-node
+adapts molejo as one leaf-geometry technology among the several it
+supports; molejo itself is independent and consumable by any Python or
+three.js project.
+
+## License
+
+Apache License 2.0 — see `LICENSE`.

molejo-0.1.0/molejo/__init__.py

@@ -0,0 +1,79 @@
+# molejo - analytic flexible parts for mechanical CAD
+# Copyright (C) 2026 Luis Henrique Cassis Fagundes
+# SPDX-License-Identifier: Apache-2.0
+
+"""Analytic flexible parts for mechanical CAD.
+
+A molejo shape is a serializable spec -- a planar profile swept along a
+parametric path whose numeric slots may reference named scalar
+parameters. This package is the Python side: the authoring layer that
+writes the spec, and the evaluator that turns spec plus parameter values
+into a deterministic triangle mesh::
+
+    from molejo import Shape, Circle, Line, P
+
+    tube = Shape(
+        profile=Circle(radius=2.0),
+        path=[Line(to=(0.0, 0.0, P.length))],
+        path_samples=8, profile_samples=32,
+    )
+    tube.to_json()            # the spec -- what a browser gets
+    mesh = tube.evaluate(length=46.8)   # numpy vertices and faces
+    mesh.to_stl()             # binary STL bytes
+
+Spec version 1 is defined in :mod:`molejo.spec` and evaluated in
+:mod:`molejo.evaluator`, which sweeps a circle or polygon profile along
+the whole v1 path vocabulary -- ``line``, ``arc``, ``helix``, ``spline``
+and ``wrap`` -- open or closed into a loop.
+
+:mod:`molejo.brep` evaluates the same documents exactly, to closed OCCT
+solids, for a consumer whose testing architecture asserts on exact
+shapes::
+
+    tube.brep(length=46.8).volume()
+
+It needs the ``brep`` extra (``pip install molejo[brep]``) and is
+imported only when asked for, so a plain install meshes and exports STL
+on numpy alone. See the repository's openspec/ records.
+"""
+
+from .authoring import (
+    Arc,
+    Circle,
+    Helix,
+    Line,
+    P,
+    ParamRef,
+    Polygon,
+    Shape,
+    Spline,
+    Teeth,
+    Wrap,
+)
+from .evaluator import EvaluationError, Mesh, evaluate
+from .spec import SPEC_VERSION, SpecError, parameter_names, validate
+
+__author__ = "Luis Henrique Cassis Fagundes"
+__email__ = "lhfagundes@gmail.com"
+__version__ = "0.1.0"
+
+__all__ = [
+    "SPEC_VERSION",
+    "Arc",
+    "Circle",
+    "EvaluationError",
+    "Helix",
+    "Line",
+    "Mesh",
+    "P",
+    "ParamRef",
+    "Polygon",
+    "Shape",
+    "SpecError",
+    "Spline",
+    "Teeth",
+    "Wrap",
+    "evaluate",
+    "parameter_names",
+    "validate",
+]