mcberk / wrapitk

Automatically exported from code.google.com/p/wrapitk
0 stars 0 forks source link

External projects should appear as a separate module in the binding language #13

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Currently, in python, external projects are added into the existing itk
package. In java binding, I have added the feature of a user-defined
package, but it needs some cmake work, and it would be good to have the
same thing for python. Perhaps the user can specify a package name as a
mandatory cmake variable.

The benefit is that the official itk package is going to be separated the
user packages, it stops the itk package to grow more than this and it also
provides a hint about installing the external packages. For instance having
something like:

import itk
import itk-numpy

provides the information that package python-itk-numpy, which is not
officially part of itk, must be installed to run this code.

Original issue reported on code.google.com by Tondd...@gmail.com on 9 Feb 2009 at 3:34

GoogleCodeExporter commented 9 years ago
On my side, I see the integration in the itk module as a feature which makes 
life way
easier while running WrapITK in the interpreter.

Also, you can already do

  import PyBuffer

if you prefer highlighting the external projects. But I'm afraid that using 
PyBuffer
(or even itk-numpy) as a prefix is not really convenient.

Original comment by gaetan.l...@gmail.com on 12 Feb 2009 at 7:26