-
Notifications
You must be signed in to change notification settings - Fork 533
Enthought Tool Suite configuration #972
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
perhaps you can see how matplotlib backends are set and perform this alongside it? |
Sure, I just wanted to propose it. If you agree, I'll get it done :) |
@satra, how could I set the environment variable |
@oesteban - you would have to do it in the environment outside. within nipype we try not to touch the environment unless necessary. |
@chrisfilo said (#1219 (comment)):
Agreed, but that is a CommandLine interface, so it has it's own environment and we can handle it. In this case, as it is a BaseInterface, the system-wide environment is used. @satra, what if we save the environment first and then we restore it after loading tvtk? |
that should work. the only thing i don't know is if multiprocessing preserves separate environments (i think it does). |
* upstream/master: Correct versions and consistency in install.rst fix:import utils needed one more dot fix: absolute to relative imports add vtk version checking in fsl interfaces update CHANGES Fix nipy#1218 only, not addressing nipy#973 force setting ETS_TOOLKIT before tvtk nipy#972 Created TVTKBaseInterface. Should fix nipy#1218
ETS should be configured to use the
null
toolkit as in https://github.com/nipy/nipype/blob/master/nipype/algorithms/mesh.py#L77. However this results in aValueError
if it is already set (which is very common with ipython).I think this setting should be done at the very beginning when importing nipype, isn't it?
The text was updated successfully, but these errors were encountered: