Difference between revisions of "2013 Project Week:PythonModules"
From NAMIC Wiki
| Line 24: | Line 24: | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
| − | * | + | * JC has implemented and documented the steps required to install external Python packages into the Slicer environment [[http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/Python_scripting#Resources]] |
| + | ==== TODO ==== | ||
| + | * Add the Python function <tt>install_distributions</tt> into the <tt>slicer.util</tt> module (rename to <tt>importExternalPythonModules()</tt> ?) | ||
| + | * Add inclusion of distribute and pip installs to the CMake build (default: OFF) | ||
</div> | </div> | ||
</div> | </div> | ||
Revision as of 15:57, 11 January 2013
Home < 2013 Project Week:PythonModules
Key Investigators
- Dave Welch, UIowa SENAP
Project Description
Objective
- Adding Python modules into the Slicer environment is currently cumbersome and difficult to do. With the growth of Python as a scientific research tool, Slicer should provide an easy mechanism for inclusion of Python modules on the fly.
- We will discuss with lead Slicer developers how to best implement a user-friendly approach to improve Python importing. Our work will be tested and documented on the Slicer wiki.
Approach, Plan
- Discussions with JC, Steve, Andrey, and interested Python programmers
- Document best approaches
- Implement work in Slicer 4.3
Progress
- JC has implemented and documented the steps required to install external Python packages into the Slicer environment [[1]]
TODO
- Add the Python function install_distributions into the slicer.util module (rename to importExternalPythonModules() ?)
- Add inclusion of distribute and pip installs to the CMake build (default: OFF)
