Skip to content

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

Closed
oesteban opened this issue Oct 20, 2014 · 6 comments · Fixed by #973
Closed

Enthought Tool Suite configuration #972

oesteban opened this issue Oct 20, 2014 · 6 comments · Fixed by #973

Comments

@oesteban
Copy link
Contributor

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 a ValueError 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?

@oesteban oesteban added this to the 0.10 milestone Oct 20, 2014
oesteban added a commit to oesteban/nipype that referenced this issue Oct 20, 2014
@satra
Copy link
Member

satra commented Oct 20, 2014

perhaps you can see how matplotlib backends are set and perform this alongside it?

@oesteban
Copy link
Contributor Author

Sure, I just wanted to propose it. If you agree, I'll get it done :)

@oesteban
Copy link
Contributor Author

@satra, how could I set the environment variable ETS_TOOLKIT='null' before anything else is executed in nipype?

@satra
Copy link
Member

satra commented Sep 16, 2015

@oesteban - you would have to do it in the environment outside. within nipype we try not to touch the environment unless necessary.

@oesteban
Copy link
Contributor Author

@chrisfilo said (#1219 (comment)):

This might be a better way of doing this: >

if ( ALT_ITKv4_THREAD_LIMIT_VARIABLE in self.inputs.environ ):

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?

@satra
Copy link
Member

satra commented Sep 17, 2015

that should work. the only thing i don't know is if multiprocessing preserves separate environments (i think it does).

@oesteban oesteban removed this from the 0.10 milestone Sep 18, 2015
satra added a commit to satra/nipype that referenced this issue Dec 12, 2015
* 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants