plc4x-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christofer Dutz <>
Subject [Python] Adding build support for Python
Date Tue, 30 Apr 2019 14:04:02 GMT
Hi all,

After streamlining the build for C++ I now started to have a look at the Python part.

So in the python world it seems as if usually a is created and then python executes
that script to build the project.
From a look at some sample python projects, it looks as if it generally contains some information
we already have in the maven metadata.

When executing an example build and looking at the result, it looked as if the build generates
a “egg” (Zip with ending “egg”) that contains unmodified versions of the sources and
resources. In addition the script seems to generate a “egg-info” directory which contains
a lot of different text files, these are then also included in the egg-zip.

So I think we have multiple options here:

  *   Have maven generate the egg-files from Maven exclusively
  *   Have maven generate a (by including data from maven to that file) and then
run “python install” which then generates everything
  *   Write a (duplicating data from the pom) and executing a python build in the
maven build

The last option has the benefit of working out of the box with Python and probably any Python
IDE (If there is such a thing) but would have the drawback that we need to manually adjust
it to pom changes (Version during releases)
The first option would eliminate the need for another build tool (but would also eliminate
the running of tests or other fancy python stuff)
The middle option would be a compromise … it wouldn’t work out of the box, but after running
“mvnw generate-resources” it could generate the missing files and the Python IDEs would
pick it up.

I think the middle approach sort of feels like the sweet spot at the moment … or am I missing
something here?
Are there other options, I didn’t mention?

What do you think?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message