{"action":"created","issue":{"url":"https://api.github.com/repos/nipy/nipype/issues/973","repository_url":"https://api.github.com/repos/nipy/nipype","labels_url":"https://api.github.com/repos/nipy/nipype/issues/973/labels{/name}","comments_url":"https://api.github.com/repos/nipy/nipype/issues/973/comments","events_url":"https://api.github.com/repos/nipy/nipype/issues/973/events","html_url":"https://github.com/nipy/nipype/pull/973","id":46424660,"number":973,"title":"[ENH] Refactor VTK and tvtk -based interfaces","user":{"login":"oesteban","id":598470,"avatar_url":"https://avatars.githubusercontent.com/u/598470?v=3","gravatar_id":"","url":"https://api.github.com/users/oesteban","html_url":"https://github.com/oesteban","followers_url":"https://api.github.com/users/oesteban/followers","following_url":"https://api.github.com/users/oesteban/following{/other_user}","gists_url":"https://api.github.com/users/oesteban/gists{/gist_id}","starred_url":"https://api.github.com/users/oesteban/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/oesteban/subscriptions","organizations_url":"https://api.github.com/users/oesteban/orgs","repos_url":"https://api.github.com/users/oesteban/repos","events_url":"https://api.github.com/users/oesteban/events{/privacy}","received_events_url":"https://api.github.com/users/oesteban/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/nipy/nipype/labels/needs%20review","name":"needs review","color":"0052cc"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2014-10-21T18:03:09Z","updated_at":"2016-02-05T15:52:23Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/nipy/nipype/pulls/973","html_url":"https://github.com/nipy/nipype/pull/973","diff_url":"https://github.com/nipy/nipype/pull/973.diff","patch_url":"https://github.com/nipy/nipype/pull/973.patch"},"body":"This PR has ended up as follows:\r\n\r\n- [x] Improve the way VTK and tvtk are loaded (created ```nipype.interfaces.vtkbase``` to encapsulate it).\r\n- [x] Improve the use of VTK and tvtk in ```algorithms.mesh``` and ```interfaces.fsl.utils```.\r\n- [x] Automate outputs/inputs decision depending on VTK version (see #1218)\r\n- [x] Set ```ETS_TOOLKIT=null``` (headless operation) before loading tvtk, then leave environment as it was before (close #972).\r\n- [x] Added VTK and tvtk in travis for python 2.7 and in circleCi. AFAIK, VTK wrapping is not quite ready in python 3.x. Before this, both travis and circle skipped tests because VTK was not found (tests had to be run locally)."},"comment":{"url":"https://api.github.com/repos/nipy/nipype/issues/comments/180411949","html_url":"https://github.com/nipy/nipype/pull/973#issuecomment-180411949","issue_url":"https://api.github.com/repos/nipy/nipype/issues/973","id":180411949,"user":{"login":"oesteban","id":598470,"avatar_url":"https://avatars.githubusercontent.com/u/598470?v=3","gravatar_id":"","url":"https://api.github.com/users/oesteban","html_url":"https://github.com/oesteban","followers_url":"https://api.github.com/users/oesteban/followers","following_url":"https://api.github.com/users/oesteban/following{/other_user}","gists_url":"https://api.github.com/users/oesteban/gists{/gist_id}","starred_url":"https://api.github.com/users/oesteban/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/oesteban/subscriptions","organizations_url":"https://api.github.com/users/oesteban/orgs","repos_url":"https://api.github.com/users/oesteban/repos","events_url":"https://api.github.com/users/oesteban/events{/privacy}","received_events_url":"https://api.github.com/users/oesteban/received_events","type":"User","site_admin":false},"created_at":"2016-02-05T15:52:23Z","updated_at":"2016-02-05T15:52:23Z","body":"@chrisfilo @satra this should be ready to go. Travis is passing (https://travis-ci.org/oesteban/nipype/builds/107064924, I don't know why it isn't shown anymore with the checks).\r\n\r\nWe have 3 'issues' for codacy, but this comes from master. I tried to solve them, but did not find the underlying problem. We should take a look on it, just in case it could derive into problems in the future."}}