Comment 14 for bug 241352

On Fri, Jun 20, 2008 at 05:28:59AM -0000, Scott Kitterman wrote:
> So this is a bug in python-enthought-traits-ui? Before we could change
> that, we'd need to understand the impacts of that on that package and
> other users of SimpleScene.

It is. This code that is in python-enthought-traits-ui should really be
moved to mayavi2. The whole ethnought.pyface.tvtk should be moved to
enthought.tvtk.pyface (whcch lives in the mayavi2 Debian package). This
is historical, because at some point we where considering these projects
as non independant. These 2 projects are a split of the same SVN for
modularity: the python-matplotlib project (to which we are not directly
related) uses the python-enthought-traits project. The
python-enthought-traits-ui project is the ui part of the
python-enthought-traits project. It is not currently used by another
Debian package, but it is used in other projects, who do not use the 3D
plotting code in mayavi2. Thus they do not want the dependency on vtk,
which is a heavy dependency. We will probably need to split the Debian
packages a bit more, as time goes on, as this code is very modular, and
there are usecases for its modularity.

As the python-vtk project as declared wxVTKRenderWindow obsolete and
unmainained, we have declared the SimpleScene obsolete and have removed
in from the api. It is still in the codebase, and can be imported
directly from its source file, but this will cause a traceback when used
with wxpython2.8.

When we did this, we surveyed our users, and the SimpleScene was not used
anywhere. People use the Scene, and so did we in mayavi.

So as a conclusion, this is an API breakage, but to react to a wxPython
API breakage, and the packages python-enthought-traits,
python-enthought-traits-ui and mayavi2 are stronly linked.

I hope the clarifies a bit things.

Cheers,

Gaël