Difference between revisions of "2013 Project Week:PythonModules"
From NAMIC Wiki
m (Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/") |
|||
| Line 27: | Line 27: | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
* JC has implemented and documented the steps required to install external Python packages into the Slicer environment | * JC has implemented and documented the steps required to install external Python packages into the Slicer environment | ||
| − | ** [[ | + | ** [[https://www.slicer.org/wiki/Documentation/Nightly/Developers/Python_scripting#Resources|Slicer Wiki documentation]] |
==== TODO ==== | ==== TODO ==== | ||
* Add the Python function <tt>install_distributions</tt> into the <tt>slicer.util</tt> module | * Add the Python function <tt>install_distributions</tt> into the <tt>slicer.util</tt> module | ||
Latest revision as of 18:07, 10 July 2017
Home < 2013 Project Week:PythonModules
Key Investigators
- Dave Welch, University of Iowa SINAPSE
- Hans Johnson, University of Iowa SINAPSE
- JC, UNC-Chapel Hill
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
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)
