Skip to content
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

Add requirements.txt #69

Merged
merged 1 commit into from
May 8, 2018
Merged

Add requirements.txt #69

merged 1 commit into from
May 8, 2018

Conversation

ihnorton
Copy link
Member

No description provided.

@ihnorton
Copy link
Member Author

@ljod @zhangfanmark this will allow pip to install dependencies. Eventually it should probably also include VTK, but leaving that off for now because of the version questions.

@ihnorton
Copy link
Member Author

(and will allow the SlicerWMA installer to avoid enumerating each dependency)

@ljod
Copy link
Member

ljod commented Apr 27, 2018

Is this for use within Slicer or general installation or both? Also, we are currently at an older VTK than Slicer. But I wonder if it is ever safe to install a VTK python package in the python that Slicer uses? Since it is also compiled as part of Slicer itself?

@ihnorton
Copy link
Member Author

Both; it would also help to make a pypi package eventually (not working on that now of course).

I wonder if it is ever safe to install a VTK python package in the python that Slicer uses?

Yeah we need to double-check compatibility with Slicer VTK.

@ljod ljod merged commit 88b3209 into SlicerDMRI:master May 8, 2018
@ihnorton ihnorton deleted the add_req_txt branch September 10, 2018 20:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants