Maintainers: @chuckatkins @danlipsa

It appears vtk restructured their python bindings starting 8.2.0 (https://blog.kitware.com/vtk-8-2-0/). However, this change is apparently not reflected in spack, and therefore, I am not getting the correct PYTHONPATH.

Steps to reproduce the issue

I can install version 8.2.0 successfully, and it puts python bindings in lib64. Upon loading the package, spack puts lib in the PYTHONPATH, and I cannot import the python package.

$ spack install [email protected] +python # i installed with +mpi+osmesa, but that should not matter here
$ spack cd -i [email protected]
$ ls lib/python3.7/site-packages/          # returns empty
$ ls lib64/python3.7/site-packages/
vtk.py	vtkmodules

$ spack load -r [email protected]
$ echo $PYTHONPATH
$SPACK_ROOT/opt/spack/linux-rhel7-broadwell/gcc-7.3.0/vtk-8.2.0-75xr5zuecmun6av2rmgbrzjammyh62sz/lib/python3.7/site-packages: .....

Here is the behavior for [email protected] (works correctly)

$ spack install [email protected] +python # i installed with +mpi+osmesa, but that should not matter here
$  spack cd -i [email protected]
$ ls lib/python3.7/site-packages/
vtk               # python package
$ ls lib64/python3.7/site-packages/          # does not exist

$ spack load -r [email protected]
$ echo $PYTHONPATH
$SPACK_ROOT/opt/spack/linux-rhel7-broadwell/gcc-7.3.0/vtk-8.1.2-6emg5zldy6rw5qgcf33x7s3unh55s6z6/lib/python3.7/site-packages: ....

Information on your system

Tried this on linux-rhel7-broadwell architecture.

General information

• I have run spack debug report and reported the version of Spack/Python/Platform
• I have run spack maintainers <name-of-the-package> and @mentioned any maintainers
• I have uploaded the build log and environment files
• I have searched the issues of this repo and believe this is not a duplicate