[go: up one dir, main page]
Menu ▾ ▴

#184 Build the Python interface with CMake

0.3.2
done
nobody
None
nobody
2020-10-05
2020-01-26
Ulf Lorenz
No
What and Why

Currently, building the Python interface is a complex multi-step procedure that goes through building and installing the main system, and then building and installing the Python interface with a different build tool (setuptools.py).

With the more recent CMake versions, there might be better support for building Python code directly. Also, we could simply skip the part where you install the Python interface as a module and instead directly copy or otherwise place the interface in the Python path. In any case, the documentation of the FindPython3() module might give some ideas on how to do this.

If we cannot build the Python interface easily with the help of CMake, at least add transitive dependencies automatically when compiling the interface.

After several tries, I decided to build the Python interface completely with Wavepacket. This feels a bit ugly on installation, but that might befit the dependencies and so on.

Breaking change: The module "wavepacket.units" is automatically imported when you import wavepacket. This changes some syntax.

Discussion

  • Ulf Lorenz

    Ulf Lorenz - 2020-07-31
    • Milestone: 0.4 goal --> 0.3.2
     

  • Ulf Lorenz

    Ulf Lorenz - 2020-09-19
    • status: open --> assigned
    • assigned_to: Ulf Lorenz
     

  • Burkhard Schmidt

    Burkhard Schmidt - 2020-10-05
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -2,7 +2,7 @@

 Currently, building the Python interface is a complex multi-step procedure that goes through building and installing the main system, and _then_ building and installing the Python interface with a different build tool (setuptools.py).

-With the more recent CMake versions, there might be better support for building Python code directly. Also, we could simply skip the part where you install the Python interfave as a module and instead directly copy or otherwise place the interface in the Python path. In any case, the documentaiton of the FindPython3() module might give some ideas on how to do this.
+With the more recent CMake versions, there might be better support for building Python code directly. Also, we could simply skip the part where you install the Python interface as a module and instead directly copy or otherwise place the interface in the Python path. In any case, the documentation of the FindPython3() module might give some ideas on how to do this.

 If we cannot build the Python interface easily with the help of CMake, at least add transitive dependencies automatically when compiling the interface.
     

  • Ulf Lorenz

    Ulf Lorenz - 2020-10-05
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -6,3 +6,6 @@

 If we cannot build the Python interface easily with the help of CMake, at least add transitive dependencies automatically when compiling the interface.

+----
+
+After several tries, I decided to build the Python interface completely with Wavepacket. This feels a bit ugly on installation, but that might befit the dependencies and so on.
    • status: assigned --> done
    • assigned_to: Ulf Lorenz --> nobody
     

  • Ulf Lorenz

    Ulf Lorenz - 2020-10-05
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -9,3 +9,5 @@
 ----

 After several tries, I decided to build the Python interface completely with Wavepacket. This feels a bit ugly on installation, but that might befit the dependencies and so on.
+
+Breaking change: The module "wavepacket.units" is automatically imported when you import wavepacket. This changes some syntax.
     

Log in to post a comment.