Python 3 wrapper not included in python-gdcm

Bug #1748411 reported by alkamid
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdcm (Debian)
Fix Released
Unknown
gdcm (Ubuntu)
Fix Released
Undecided
Debian Med

Bug Description

Python 3 wrappers for gdcm are readily available when compiling from source. In cmake config, the following options should be set:

GDCM_BUILD_SHARED_LIBS=ON
GDCM_WRAP_PYTHON=ON
CMAKE_BUILD_TYPE=RELEASE

Also PYTHON_EXECUTABLE, PYTHON_INCLUDE_DIR and PYTHON_LIBRARY should be set accordingly. I generated the wrappers under Python 3.6 and successfully tested them on JPEG2000 compressed dicoms. .py files and the library attached.

Could the maintainers add Python 3 version to this package? (Alternatively, should python3-gdcm package be created?)

Revision history for this message
alkamid (adamkli) wrote :

Attached wrappers build from 2.6.4 source (v2.6.3 had a bug with documentation building on Ubuntu 16.04).

Dylan Aïssi (daissi)
Changed in gdcm (Ubuntu):
assignee: nobody → Debian Med (debian-med)
Revision history for this message
Gert Wollny (gert-die) wrote :

In the debian/rules file it is stated:

# Need to make sure to build using the same vtk/python version:

This is from the previous maintainer who is also upstream, so I guess he knows what he is talking about. The current version of VTK in Debian is VTK6, and this version doesn't support python3.

VTK7, which supports python3 is stuck in the Debian new pipeline and we have to wait until this new package is accepted until we can move gdcm to python3.

Revision history for this message
alkamid (adamkli) wrote :

Gert, could you please elaborate on this? In order to generate *Python wrappers* for GDCM, as far as I understand you don't need a Python 3-compatible VTK version. What you need is a SWIG version compatible with py3k, but that's already satisfied in 16.04.

Maybe you're talking about python-vtkgdcm, not python-gdcm?

Revision history for this message
Dylan Aïssi (daissi) wrote :

Fixed in 2.8.7-2, so at least in Disco.

Changed in gdcm (Ubuntu):
status: New → Fix Committed
Changed in gdcm (Debian):
status: Unknown → Fix Released
Revision history for this message
alkamid (adamkli) wrote :

Any chance of upgrading to 2.8.7-2 in Bionic, given that py3k is the default since 18.04?

Dylan Aïssi (daissi)
Changed in gdcm (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.