cppdantic 0.0.7__tar.gz

cppdantic-0.0.7/.github/workflows/publish.yml

@@ -0,0 +1,50 @@
+# sdist + manylinux_2_28 x86_64 wheels (cibuildwheel), upload to PyPI on tag v*.
+# Requires repository secret: PYPI_API_TOKEN
+
+name: Publish to PyPI
+
+on:
+  push:
+    tags:
+      - "v*"
+
+permissions:
+  contents: read
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      # Independent package: install easybind from PyPI, then poll until pins resolve.
+      - name: Wait for pinned easybind on PyPI
+        run: |
+          python -m pip install "easybind~=0.2.14"
+          easybind-wait-pypi
+
+      - name: Install build tools
+        run: pip install --upgrade build twine
+
+      - name: Build sdist
+        run: python -m build --sdist
+
+      - name: Build manylinux wheels
+        uses: pypa/cibuildwheel@v3.4.0
+
+      - name: Stage wheels next to sdist
+        run: cp wheelhouse/*.whl dist/
+
+      - name: Check distributions
+        run: twine check dist/*
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          password: ${{ secrets.PYPI_API_TOKEN }}

cppdantic-0.0.7/.gitignore

@@ -0,0 +1,212 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+uv.lock
+
+# C extensions
+*.so
+
+# nanobind stubgen (regenerated by CMake `nanobind_add_stub`)
+src/cppdantic/__init__.pyi
+
+# setuptools-scm (see RELEASING.md)
+src/cppdantic/_version.py
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV — not committing the lockfile for this project
+uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+#poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+#pdm.lock
+#pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+#pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Abstra
+# Abstra is an AI-powered process automation framework.
+# Ignore directories containing user credentials, local state, and settings.
+# Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#  Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#  that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#  and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#  you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor
+#  Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
+#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
+#  refer to https://docs.cursor.com/context/ignore-files
+.cursorignore
+.cursorindexingignore
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/

cppdantic-0.0.7/.gitmodules

@@ -0,0 +1,3 @@
+[submodule "external/easybind"]
+	path = external/easybind
+	url = https://github.com/pymergetic/easybind

cppdantic-0.0.7/CMakeLists.txt

@@ -0,0 +1,47 @@
+cmake_minimum_required(VERSION 3.25)
+
+project(cppdantic LANGUAGES CXX)
+
+set(CMAKE_CXX_STANDARD 20)
+set(CMAKE_CXX_STANDARD_REQUIRED ON)
+
+include(GNUInstallDirs)
+
+find_package(Python REQUIRED COMPONENTS Interpreter Development.Module)
+execute_process(
+    COMMAND "${Python_EXECUTABLE}" -c
+        "import pathlib, easybind; print(pathlib.Path(easybind.__file__).resolve().parent / 'cmake' / 'easybind_pip.cmake')"
+    OUTPUT_STRIP_TRAILING_WHITESPACE
+    OUTPUT_VARIABLE _eb_pip
+    COMMAND_ERROR_IS_FATAL ANY
+)
+include("${_eb_pip}")
+easybind_pip_setup()
+easybind_fetch_magic_enum()
+
+nanobind_add_module(cppdantic__init__ NB_SHARED src/cppdantic/hello.cpp)
+target_include_directories(cppdantic__init__ PRIVATE "${EASYBIND_INCLUDE_ROOT}")
+target_link_libraries(cppdantic__init__ PRIVATE "${EASYBIND_CORE_LIB}")
+easybind_pip_link_magic_enum(cppdantic__init__)
+
+set_target_properties(cppdantic__init__ PROPERTIES
+    OUTPUT_NAME "__init__"
+    LIBRARY_OUTPUT_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}/cppdantic"
+    RUNTIME_OUTPUT_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}/cppdantic"
+)
+
+easybind_pip_set_rpath_next_to_easybind(cppdantic__init__ "${EASYBIND_PKG_DIR}")
+
+# Typings for editors / type checkers (same mechanism as easybind: nanobind_add_stub).
+set(_cppdantic_pyi "${CMAKE_CURRENT_SOURCE_DIR}/src/cppdantic/__init__.pyi")
+get_filename_component(_cppdantic_pyi_dir "${_cppdantic_pyi}" DIRECTORY)
+file(MAKE_DIRECTORY "${_cppdantic_pyi_dir}")
+nanobind_add_stub(cppdantic_stub
+    MODULE cppdantic
+    OUTPUT ${_cppdantic_pyi}
+    PYTHON_PATH $<TARGET_FILE_DIR:cppdantic__init__>
+    DEPENDS cppdantic__init__
+)
+
+install(TARGETS cppdantic__init__ LIBRARY DESTINATION cppdantic)
+install(FILES ${_cppdantic_pyi} DESTINATION cppdantic)

cppdantic-0.0.7/LICENSE

@@ -0,0 +1,201 @@
+                                 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.

cppdantic-0.0.7/PKG-INFO

@@ -0,0 +1,75 @@
+Metadata-Version: 2.4
+Name: cppdantic
+Version: 0.0.7
+Summary: Hello-world nanobind extension built against the easybind package (demo / CI smoke test)
+Keywords: cppdantic,nanobind,easybind,bindings,pymergetic
+Author-Email: PymergeticOS Maintainers <raudzus@pymergetic.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: C++
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Typing :: Typed
+Project-URL: Homepage, https://github.com/pymergetic/cppdantic
+Project-URL: Repository, https://github.com/pymergetic/cppdantic
+Project-URL: Issues, https://github.com/pymergetic/cppdantic/issues
+Requires-Python: >=3.11
+Requires-Dist: easybind~=0.2.15
+Provides-Extra: test
+Requires-Dist: pytest>=7.0.0; extra == "test"
+Requires-Dist: scikit-build-core>=0.10; extra == "test"
+Requires-Dist: setuptools-scm>=8; extra == "test"
+Description-Content-Type: text/markdown
+
+# cppdantic
+
+Small demo that **builds against the `easybind` package from PyPI**. **cppdantic** and **easybind** are **independent** projects (separate repos, separate PyPI names). This repo may include **`external/easybind`** as an **optional git submodule** only so you can browse both trees in one checkout — it is **not** wired into `pyproject.toml` as a path dependency.
+
+**PyPI:** [`cppdantic`](https://pypi.org/project/cppdantic/) (when published). Versioning and tags: **`RELEASING.md`**.
+
+**Bumping `easybind~=…`:** **`easybind-pin-pyproject`** (from **easybind**). Default = latest **`v*`** tag on **GitHub** (repo URL from that package’s PyPI metadata). Use **`--from-pypi`** for PyPI’s published latest instead — see **`RELEASING.md`**.
+
+## Build / test
+
+You need **`easybind`** installed from **PyPI** (matching the pin in **`pyproject.toml`**), plus CMake ≥ 3.25, Ninja, and a C++20 compiler on `PATH`:
+
+```bash
+python -m pip install -U pip
+python -m pip install "easybind~=0.2.14"   # align with pyproject.toml
+python -m pip install -e '.[test]'
+python -m pytest tests -q
+```
+
+`CMake` loads **`easybind/cmake/easybind_pip.cmake`** from the **installed** **`easybind`** package. PyPI must ship the **`cmake/`** tree for the version you pin.
+
+**Optional submodule:** if you use **`git submodule update --init external/easybind`**, you can also **`pip install -e /path/to/easybind`** from that checkout — it is the same **easybind** project, not a special cppdantic path override.
+
+### uv
+
+From the **cppdantic repo root**:
+
+```bash
+uv pip install "easybind~=0.2.14"
+uv pip install -e ".[test]"
+```
+
+(`pyproject.toml` sets **`[tool.uv] no-build-isolation-package = ["cppdantic"]`** so editable builds use your venv; the **`[test]`** extra pulls in **`setuptools-scm`** and **`scikit-build-core`** for that mode.)
+
+If **`uv pip install`** fails with **`Metadata mismatch in METADATA`** (setuptools-scm version differs between build phases), clear stale artifacts and install **easybind first**, then **cppdantic**:
+
+```bash
+rm -rf build dist *.egg-info src/cppdantic/*.egg-info
+uv pip install -e external/easybind/
+uv pip install -e ".[test]"
+```
+
+Ensure **`src/cppdantic/_version.py`** is not tracked by git (it is gitignored). If it was ever committed, run **`git rm --cached src/cppdantic/_version.py`**.
+
+## Tagging
+
+Create an annotated **`v*`** tag on **`main`** after your pins commit (see **`RELEASING.md`**).

cppdantic-0.0.7/README.md

@@ -0,0 +1,47 @@
+# cppdantic
+
+Small demo that **builds against the `easybind` package from PyPI**. **cppdantic** and **easybind** are **independent** projects (separate repos, separate PyPI names). This repo may include **`external/easybind`** as an **optional git submodule** only so you can browse both trees in one checkout — it is **not** wired into `pyproject.toml` as a path dependency.
+
+**PyPI:** [`cppdantic`](https://pypi.org/project/cppdantic/) (when published). Versioning and tags: **`RELEASING.md`**.
+
+**Bumping `easybind~=…`:** **`easybind-pin-pyproject`** (from **easybind**). Default = latest **`v*`** tag on **GitHub** (repo URL from that package’s PyPI metadata). Use **`--from-pypi`** for PyPI’s published latest instead — see **`RELEASING.md`**.
+
+## Build / test
+
+You need **`easybind`** installed from **PyPI** (matching the pin in **`pyproject.toml`**), plus CMake ≥ 3.25, Ninja, and a C++20 compiler on `PATH`:
+
+```bash
+python -m pip install -U pip
+python -m pip install "easybind~=0.2.14"   # align with pyproject.toml
+python -m pip install -e '.[test]'
+python -m pytest tests -q
+```
+
+`CMake` loads **`easybind/cmake/easybind_pip.cmake`** from the **installed** **`easybind`** package. PyPI must ship the **`cmake/`** tree for the version you pin.
+
+**Optional submodule:** if you use **`git submodule update --init external/easybind`**, you can also **`pip install -e /path/to/easybind`** from that checkout — it is the same **easybind** project, not a special cppdantic path override.
+
+### uv
+
+From the **cppdantic repo root**:
+
+```bash
+uv pip install "easybind~=0.2.14"
+uv pip install -e ".[test]"
+```
+
+(`pyproject.toml` sets **`[tool.uv] no-build-isolation-package = ["cppdantic"]`** so editable builds use your venv; the **`[test]`** extra pulls in **`setuptools-scm`** and **`scikit-build-core`** for that mode.)
+
+If **`uv pip install`** fails with **`Metadata mismatch in METADATA`** (setuptools-scm version differs between build phases), clear stale artifacts and install **easybind first**, then **cppdantic**:
+
+```bash
+rm -rf build dist *.egg-info src/cppdantic/*.egg-info
+uv pip install -e external/easybind/
+uv pip install -e ".[test]"
+```
+
+Ensure **`src/cppdantic/_version.py`** is not tracked by git (it is gitignored). If it was ever committed, run **`git rm --cached src/cppdantic/_version.py`**.
+
+## Tagging
+
+Create an annotated **`v*`** tag on **`main`** after your pins commit (see **`RELEASING.md`**).

cppdantic-0.0.7/RELEASING.md

@@ -0,0 +1,117 @@
+# Releasing cppdantic to PyPI
+
+**Pins vs installs:** **`easybind-pin-pyproject`** (default) sets pins from the **latest `v*`** tag on **GitHub**. **cppdantic** still **builds and ships wheels that `pip install easybind`** — that means **PyPI**. Wait until the pinned **`easybind==A.B.C`** exists on PyPI before you rely on isolated installs or CI (see **`easybind-wait-pypi`** in cppdantic’s publish workflow).
+
+## End-to-end workflow (easybind → PyPI → bump cppdantic → tag)
+
+Do this in order.
+
+### 1) Release **easybind** (separate repo; submodule path shown for this monorepo)
+
+```bash
+cd /path/to/easybind   # e.g. ~/Devel/cppdantic/external/easybind
+
+git fetch origin && git checkout main && git pull origin main
+# commit anything not on main, then:
+
+export EB_TAG=v0.2.4    # choose the new version
+git tag -a "$EB_TAG" -m "easybind ${EB_TAG#v}"
+git push origin main
+git push origin "$EB_TAG"
+```
+
+- Wait until GitHub **Publish to PyPI** on **easybind** finishes.
+- Check PyPI: **https://pypi.org/project/easybind/** shows **`easybind==`** that version (or `pip install 'easybind==…'` in a clean venv).
+
+### 2) Bump **cppdantic** `pyproject.toml` pins (manual; not CI)
+
+```bash
+cd /path/to/cppdantic
+python -m pip install -U "easybind"   # refresh devtools / metadata helpers
+
+easybind-pin-pyproject --dry-run
+easybind-pin-pyproject                  # sets all easybind~= lines to latest GitHub v* tag (or: --version A.B.C)
+
+git add pyproject.toml
+git commit -m "Bump easybind pins"
+git push origin main
+```
+
+### 3) Tag **cppdantic**
+
+Bump the next **`vMAJOR.MINOR.PATCH`** from the latest **`v*`** tag (usually **patch**). Example:
+
+```bash
+cd /path/to/cppdantic
+git fetch --tags
+export TAG=v0.1.1   # choose the next version
+git tag -a "$TAG" -m "cppdantic ${TAG#v}"
+git push origin main
+git push origin "$TAG"
+```
+
+**GitHub vs PyPI:** the cppdantic tag can exist while the publish workflow fails; **`PYPI_API_TOKEN`** must be set on the **cppdantic** repo. Do not tag **cppdantic** for a pin you cannot **`pip install`** yet — CI uses **`easybind-wait-pypi`** so the workflow waits for PyPI.
+
+**CI wait:** the **Publish to PyPI** workflow installs **easybind** from PyPI and runs **`easybind-wait-pypi`** (same behavior as easybind’s wait script): it polls until **`easybind==X.Y.Z`** from your pins exists (default timeout 30 minutes, 30 s interval). Keep the **`pip install "easybind~=…"`** line in **`.github/workflows/publish.yml`** in sync with **`pyproject.toml`** when you bump pins. **No git submodule** is required for cppdantic CI.
+
+---
+
+## Order: easybind first, then bump pins
+
+**cppdantic** builds against whatever **`easybind`** you install; CI and wheels must see a matching release on PyPI.
+
+1. **easybind** (separate repo): merge your changes, tag **`vA.B.C`**, **`git push origin vA.B.C`**, and wait until the **Publish to PyPI** workflow finishes and **`easybind==A.B.C`** is installable from PyPI.
+2. **cppdantic**: bump **every** `easybind~=…` in **`pyproject.toml`** (same `A.B.C` in all three places: **`[build-system] requires`**, **`dependencies`**, **`[tool.cibuildwheel.linux] test-requires`**). Automate with **easybind**’s helper (after `pip install easybind` in your venv):
+
+   ```bash
+   cd /path/to/cppdantic
+   easybind-pin-pyproject --dry-run   # preview (default: latest v* tag on GitHub)
+   easybind-pin-pyproject             # pins follow GitHub tags (PyPI metadata supplies github.com/…)
+   ```
+
+   **`--from-pypi`:** use this if you want pins to match PyPI’s **published** latest (`info.version`) instead of the highest **`v*`** tag on GitHub (e.g. conservative bumps, or no GitHub URL in metadata — then set **`--from-github YOUR_ORG/easybind`** or fix PyPI project URLs).
+
+   Set **`GITHUB_TOKEN`** if the repo is private or you hit rate limits. Pin manually when needed: **`--version 0.2.6`**. **`--installed`** only helps after **`pip install`** has that version in the venv.
+
+   Before tagging **cppdantic**, ensure the pinned **`easybind==A.B.C`** is on **PyPI** if you expect **`pip install`** / CI to succeed.
+
+   Or import **`easybind.devtools`** — see **easybind**’s README.
+
+   **This is not run by CI or by `pip install`.** It only changes files when **you** run it and **commit** the diff. Builds always use whatever **`easybind~=…`** is already in **`pyproject.toml`** on that commit.
+
+3. **Commit that bump on `main` before you create the cppdantic tag.** The tag must point at a commit that already contains the updated **`pyproject.toml`**.
+
+If you tag cppdantic before the matching easybind wheel exists, isolated builds and cibuildwheel tests can fail.
+
+## Version
+
+Setuptools-scm reads **cppdantic**’s version from **`TAG`** only. **`easybind~=…`** must already be committed and resolvable on PyPI.
+
+Versions come from **Git tags** via **setuptools-scm** (same idea as easybind):
+
+- Tag **`vMAJOR.MINOR.PATCH`** (e.g. `v0.1.0`) on the commit you want to release.
+- On that exact tag, the sdist/wheel version is **`MAJOR.MINOR.PATCH`** (`no-guess-dev` + `no-local-version`).
+- Untagged trees get a dev version (fine for local installs; for PyPI, tag cleanly).
+
+The wheel metadata version comes from setuptools-scm (no checked-in **`_version.py`** — avoids editable-install metadata mismatches; use **`importlib.metadata.version("cppdantic")`** at runtime).
+
+## CI publish
+
+Pushing a tag **`v*`** runs **`.github/workflows/publish.yml`**: sdist, **cibuildwheel** (manylinux\_2\_28 x86\_64), **twine check**, upload to PyPI.
+
+Set the **`PYPI_API_TOKEN`** repository secret (scoped to this project).
+
+## Manual dry run
+
+```bash
+python -m pip install build twine
+git fetch --tags
+python -m build
+twine check dist/*
+# twine upload dist/*
+```
+
+## Notes
+
+- **Runtime:** the extension expects **`easybind`** installed at the version pinned in **`pyproject.toml`** (e.g. `easybind~=0.2.14`) so **`libeasybind.so`** and headers resolve next to **`site-packages/easybind`** (RPATH **`$ORIGIN/../easybind`**).
+- **Wheels** are Linux x86\_64 manylinux for now; extend the workflow if you need macOS/Windows.

cppdantic-0.0.7/pyproject.toml

@@ -0,0 +1,92 @@
+[build-system]
+requires = ["scikit-build-core>=0.10", "setuptools-scm>=8", "easybind~=0.2.15"]
+build-backend = "scikit_build_core.build"
+
+# uv: build cppdantic in the project venv so `import easybind` matches your editable easybind (see README).
+# With no-build-isolation, [build-system] deps are not installed into the venv automatically — install them
+# (e.g. via optional-deps below) before `uv pip install -e .`.
+[tool.uv]
+no-build-isolation-package = ["cppdantic"]
+
+[project]
+name = "cppdantic"
+dynamic = ["version"]
+description = "Hello-world nanobind extension built against the easybind package (demo / CI smoke test)"
+readme = "README.md"
+requires-python = ">=3.11"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+authors = [
+  { name = "PymergeticOS Maintainers", email = "raudzus@pymergetic.com" }
+]
+keywords = ["cppdantic", "nanobind", "easybind", "bindings", "pymergetic"]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+  "Programming Language :: Python :: 3.14",
+  "Programming Language :: C++",
+  "Operating System :: POSIX :: Linux",
+  "Typing :: Typed",
+]
+
+dependencies = ["easybind~=0.2.15"]
+
+[project.urls]
+Homepage = "https://github.com/pymergetic/cppdantic"
+Repository = "https://github.com/pymergetic/cppdantic"
+Issues = "https://github.com/pymergetic/cppdantic/issues"
+
+[project.optional-dependencies]
+# scikit-build-core + setuptools-scm: required in the venv for editable builds when using no-build-isolation.
+test = [
+    "pytest>=7.0.0",
+    "scikit-build-core>=0.10",
+    "setuptools-scm>=8",
+]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+
+# Linux wheels: see .github/workflows/publish.yml
+[tool.cibuildwheel]
+build = "cp311-* cp312-* cp313-* cp314-*"
+skip = "*musllinux*"
+manylinux-x86_64-image = "manylinux_2_28"
+build-verbosity = 1
+
+[tool.cibuildwheel.linux]
+# Install easybind into the container Python so libeasybind.so / libnanobind.so exist on disk.
+# auditwheel repair cannot see libs that only existed in PEP517 build isolation; it needs paths
+# like site-packages/easybind/ on LD_LIBRARY_PATH.
+before-build = [
+    "python -m pip install --upgrade pip",
+    "python -m pip install 'cmake>=3.25' ninja 'easybind~=0.2.15'",
+]
+repair-wheel-command = "python -m pip install -q --upgrade 'easybind~=0.2.15' 'auditwheel>=6.4' && EB=$(python -c 'import pathlib, easybind; print(pathlib.Path(easybind.__file__).resolve().parent)') && LD_LIBRARY_PATH=\"$EB:${LD_LIBRARY_PATH:-}\" python -m auditwheel -v repair --plat manylinux_2_28_x86_64 -w {dest_dir} {wheel}"
+test-requires = ["pytest>=7.0.0", "easybind~=0.2.15"]
+test-command = "python -m pytest {project}/tests -q"
+
+[tool.scikit-build]
+cmake.version = ">=3.25"
+logging.level = "INFO"
+minimum-version = "0.10"
+metadata.version.provider = "scikit_build_core.metadata.setuptools_scm"
+build-dir = "build"
+
+[tool.scikit-build.cmake.define]
+CMAKE_EXPORT_COMPILE_COMMANDS = "ON"
+
+[tool.scikit-build.wheel]
+packages = { "cppdantic" = "src/cppdantic" }
+
+[tool.setuptools_scm]
+version_scheme = "no-guess-dev"
+local_scheme = "no-local-version"
+fallback_version = "0.0.0"
+root = "."
+# Do not set version_file/write_to here: scikit-build-core calls setuptools-scm twice for editable
+# installs (metadata + wheel). Writing _version.py between calls can change git/dirty state and
+# trigger "Metadata mismatch" (e.g. devN vs devN+1). Use importlib.metadata.version("cppdantic") at runtime.

cppdantic-0.0.7/src/cppdantic/hello.cpp

@@ -0,0 +1,6 @@
+#include <easybind/bind.hpp>
+
+EASYBIND_NS_MODULE_SHARED_OBJECT(cppdantic, cppdantic, m, true, {
+  m.doc() = "cppdantic hello-world (built against PyPI easybind)";
+  m.def("hello", []() { return std::string("hello from cppdantic"); });
+});

cppdantic-0.0.7/tests/test_hello.py

@@ -0,0 +1,4 @@
+def test_hello():
+    import cppdantic
+
+    assert cppdantic.hello() == "hello from cppdantic"