Skip to content

Nanobind migration discussion #101

Description

@vincefn

@sbillinge this is to discuss the (possible) migration to nanobind instead of boost.python, e.g. as implemented in the nanobind_migration test branch

Please really consider this as a tentative organisation - I did this as a summer job and as a large vibe-coding exercise, so no worries if it does not match what you would like, it can be redone with different principles.

The main points are:

  • switch to nanobind
  • objcryst++ as submodule and cctbx/newmat code directly embedded, so no more need of libobjcryst
  • pyproject.toml and cmake for compilation (I don't know if you want to stick with scons
  • so far only tested on mac and linux

Also see the extended migration notes (rationale for various implementation decisions, issues with inheritance, etc..)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions