Nanobind

Latest version: v2.2.0

Safety actively analyzes 682457 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 6 of 6

0.0.4

----------------------------

* Botched release, replaced by 0.0.5 on the same day.

0.0.3

----------------------------

* DLPack support.
* Iterators for various Python type wrappers.
* Low-level interface to instance creation.
* Docstring generation improvements.
* Various minor fixes and improvements.

0.0.2

----------------------------

* Initial release of the nanobind codebase.
* ABI version 1.

0.0.1

----------------------------

* Placeholder package on PyPI.


How to make a new release?
--------------------------

1. Ensure that the full version of nanobind is checked out (including the
``robin_map`` submodule)

2. Update version in ``src/__init__.py``, ``include/nanobind/nanobind.h``,
and ``pyproject.toml``:

Also:

- Remove ``dev1`` suffix from ``X.Y.Zdev1`` in ``src/__init__.py`` and
``pyproject.toml``.

- Set ``NB_VERSION_DEV`` to ``0`` in ``include/nanobind/nanobind.h``.

3. Add release date to ``docs/changelog.rst``.

4. Update ``setup.py`` if new directories were added (see ``package_data``).
Update ``cmake/nanobind-config.cmake`` if new C++ source or header files
were added.

5. Commit: ``git commit -am "vX.Y.Z release"``

6. Tag: ``git tag -a vX.Y.Z -m "vX.Y.Z release"``

7. Push: ``git push`` and ``git push --tags``

8. Run ``pipx run build``

9. Upload: ``twine upload --repository nanobind <filename>``

10. Update version in ``src/__init__.py`` and ``include/nanobind/nanobind.h``:

- Append ``dev1`` suffix from ``X.Y.Zdev1`` in ``src/__init__.py`` and
``pyproject.toml``.

- Set ``NB_VERSION_DEV`` to ``1`` in ``include/nanobind/nanobind.h``

Page 6 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.